Backplane nodes for blind mate adapting field replaceable units to bays in storage rack

ABSTRACT

A system for the management of rack-mounted field replaceable units (FRUs) that affords the enhanced availability and serviceability of FRUs provided by blade-based systems but in a manner that accommodates different types of FRUs (e.g., in relation to form factors, functionality, power and cooling requirements, and/or the like) installed within a rack or cabinet.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 13/780,916, entitled “COMPUTING RACK-BASED VIRTUAL BACKPLANEFOR FIELD REPLACEABLE UNITS,” and filed on Feb. 28, 2013, the entirecontents of which are incorporated herein as if set forth in full.

BACKGROUND

1. Field of the Invention

The present invention generally relates to the management of fieldreplaceable units (FRUs) mounted within a frame structure such as a rackor cabinet and, more specifically, to systems and methods that bring theenhanced availability and serviceability of blade or chassis-basedcomputing systems into rack-based computing systems.

2. Relevant Background

There has been significant progress made in recent years in usingIntelligent Platform Management Interface (IPMI) for “out of band” (OOB)management (e.g., presence detection such as FRU discovery, inventoryaudit, activation such as power-cycle and CPU reset, etc.) in both rackmounted server (RMS) and blade compute systems. IPMI is an industrystandard, computer system technology providing an architecture orprotocol that facilitates communication between a system controller ormanager (e.g., including management software) and one or more uniquedevices being managed (e.g., one or more FRUs).

Computing cabinets or racks are standardized frames that are designed tohold a plurality of FRUs or related components (e.g., rack-mountedservers, power distribution units or backup devices, and/or the like).Generally, a computing rack includes a number of vertical rails or posts(e.g., two, four) to which horizontal members and rail assemblies can besecured to define a plurality of receiving bays for receiving FRUs.Various types and sizes of FRUs may be installed within a rack systemand often have standardized heights as multiples of one rack unit (U).For instance, industry standard rack systems often come in heights of18U, 22U, 36U, 42U, and the like. In high availability environments(e.g., telecommunications systems), the set of FRUs (e.g., computingdevices, related components, and the like) in a frame configuration areadministered as a single compute system that is functionally consistentwith administration of a single FRU.

More recently, FRUs such as blade servers are being used that aretypically installed within a compartment or structure referred to as a“blade enclosure” or chassis (e.g., where the blade servers andenclosure are collectively called a “blade system”). The blade enclosureincludes a midplane into which all of the blade servers areinterconnected and provides many non-core computing services toinstalled blade servers such as power, cooling, interconnects,management, and the like. That is, the installed blade serverscollectively share such non-core computing services provided by theblade enclosure. For instance, a blade enclosure may have a systemcontroller or manager including any appropriate control software orlogic that functions to intelligently adjust liquid cooling systems tomeet the cooling requirements of the blade servers. Also, the systemcontroller facilitates the ability to “hot-swap” blades within theenclosure (i.e., the ability to add, remove and replace units at needwithout having to power-off the enclosure). The AdvancedTelecommunications Computing Architecture (ATCA) is an open industrystandard including a series of specifications targeted to requirementsfor blades and chasses (e.g., in relation to form factors and the like).

SUMMARY

Blade systems advantageously provide almost 100% uptime or availabilitydue to use of a unified management service, redundancy or availability(e.g., upon a first blade server going down, a second blade server cantake over and maintain the system without interruption to other bladeservers until the first blade server is replaced), rapid faultisolation, low mean time to repair, midplane management paths tocomponents, fixed FRU locations and configurations, reductions incabling, power, and size requirements, and the like. However, bladeenclosures and the installed blade servers are typically proprietarydesigns. That is, a particular blade enclosure is usually designed toaccept only a particular type of blade server such that all of the bladeservers installed within a blade enclosure have the same form factors,connectors, and the like. Thus, the above-discussed benefits andadvantages of blade systems are inherently limited to a common type ofFRU installed within a proprietary blade enclosure. Furthermore, bladesystems typically have fixed power budgets, cooling capacities, and thelike. While upgrading to future blade designs may be possible, any suchfuture blades would be limited by the original blade design chassis forpower and cooling.

The inventors have determined that it would be desirable to bring manyof the benefits of blade or chassis-based computing systems (such as theabove-discussed enhanced availability and serviceability) intorack-based systems, but free of all or many of the limitations ofblade-based systems. Stated differently, the inventors have determinedthat it would be desirable to provide the ability to seamlessly providecentral, OOB management (e.g., in relation to rebooting, shutdown,power-on, fan speeds, power and cooling monitoring, hot-swapping, andthe like) of what may be numerous disparate FRUs (e.g., with numerousdifferent form factors, power and cooling requirements, and/or the like)within a rack-based system. That is, it would be desirable combine thehigh level of serviceability and availability of blade-based systemswith the upgrade capability of rack-mount systems.

In this regard, disclosed herein are systems and methods for themanagement of rack-mounted FRUs that afford the enhanced availabilityand serviceability of FRUs provided by blade-based systems but in amanner that accommodates different types of FRUs (e.g., in relation toform factors, functionality, power and cooling requirements, and thelike) installed within a rack or cabinet (e.g., server or open computeequipment rack, cabinet or assembly for holding a plurality of pieces ofcomputing equipment, etc.). Broadly, the disclosed system (e.g., frame)includes a plurality of “frame backplane segments,” “virtual slots” or“frame arms” (used interchangeably herein, e.g., nodes, receivingstructures, housings, connectors, and/or the like) disposable at fixedlocations within a rack, each for receiving and electricallyinterconnecting with a corresponding one of a plurality of FRUs (e.g.,having similar or disparate form factors, functionalities, etc.), andeach storing data (e.g., in a memory of the virtual slot) indicating theparticular fixed location of the virtual slot within the rack (e.g.,relative to the fixed locations of other virtual slots within the rack).Each virtual slot may be fixed to the rack adjacent a rear portion of arespective one of a plurality of receiving bays and may include aconnector (e.g., blind-mate connector) that is configured to interfacewith a corresponding connector of a FRU as the FRU is slid into thereceiving bay. For instance, each virtual slot may be configured todetect when a FRU has been inserted into its respective receiving bay(i.e., detect a presence of the FRU within the receiving bay) andtransmit one or more corresponding alerts throughout the system as willbe discussed below.

The disclosed system may include a “frame center” (e.g., a separate,dedicated computing device or system, such as a central managementserver, which may also be a FRU) that is electrically interconnectableto each of the virtual slots in a manner that allows for FRU presencedetection (i.e., receipt of a FRU in one of the receiving bays), FRU OOBmanagement (e.g., via a “frame manager” or “rack manager” implemented ator otherwise in communication with the frame center), and the like. Forinstance, the frame center may be electrically interconnected to each ofthe virtual slots by a plurality of a first type of communication paths(e.g., I²C cables) allowing for presence detection and the like, wherethe plurality of first type of communication paths may form a firstcommunication network interconnecting the frame center and frame arms.The frame center may also be electrically interconnected to each of thevirtual slots by a plurality of a second type of communication paths(e.g., network lines such as Ethernet cables) that allows for OOBmanagement communications between the frame center and frame arms aswell as non-OOB management communications to be conducted between theframe arms and devices and processes outside of the frame/system (viathe frame center). Each of the virtual slots and the frame center mayalso be electrically interconnected (e.g., via power lines or cables) toone or more (such as first and second redundant) power distributionunits (PDUs, which in turn may be appropriately electricallyinterconnected to one or more power sources) for distributing power toFRUs interfaced with the virtual slots (in addition to the framecenter).

The various cables, paths and/or lines connected between the virtualslots, the frame center and the PDUs may be considered a “fixedinterconnect topology” (e.g., wired and/or wireless) of the system orframe that allows the frame center to determine the physical or fixedlocations of installed FRUs in the rack (e.g., even among a plurality ofdisparate FRUs) via the location information stored in the memories oftheir respective virtual slots for use in conducting OOB management ofthe FRUs. A computing rack or cabinet may be pre-configured (e.g.,pre-wired) with the fixed interconnect topology so that FRUssubsequently installed (i.e., after the pre-configuring) into the rackand electrically interfaced with respective frame arms (e.g, viacorresponding blind-mate connectors of the FRUs and frame arms) cansubstantially seamlessly or automatically receive power, join themanagement network of the rack (e.g., as coordinated by the framecenter), and/or send and receive actual data signals, all free ofnecessarily having to (e.g., manually) run and interconnect a pluralityof cords and cables between the FRUs and network switches, otherservers, and/or the like (e.g., such as after and/or during insertion ofthe FRUs into the rack). In this regard, the fixed interconnect topologyand frame arms may essentially function as a “virtual backplane” ormidplane of the system. The system may be incorporated into a rack aspart of building the rack or else be retrofitted or otherwise integratedinto an existing rack. The system and rack may collectively be referredto as a “setup.”

A frame manager may communicate with OOB service processors of each ofthe FRUs (e.g., built-in system management tools each including one ormore dedicated processors and memory modules, such as Oracle'sIntegrated Lights-Out Managers (ILOMs)) via the frame center (e.g., aservice processor of the frame center) and the fixed interconnecttopology as part of performing OOB management. The system mayincorporate a unified management system (UMS) made up various piece oflogic or software executed by the frame center, the various FRU OOBservice processors, and/or higher level processors. For instance,installing a FRU into a receiving bay of a rack and interconnecting theFRU with a respective frame arm may cause a portion of the UMS to beautomatically downloaded onto the FRU for use by the FRU's OOB serviceprocessor as part of communicating with the frame manager; in thisregard, a FRU may be able to substantially automatically and seamlesslyjoin its appropriate management service context (e.g., UMS),substantially regardless of the type of FRU, form factor of the FRU,and/or the like.

As an example, imagine that a FRU is installed into a receiving bay of acomputing rack so that the above-described connector of the FRUinterconnects with a corresponding connector of the particular frame armof the receiving bay. Upon detection of a presence of the FRU (e.g., bycircuitry of the frame arm, such as by detecting a power draw by theFRU), the frame arm may send an alert (e.g., an interrupt) over thefixed interconnect topology to the frame center (e.g., over therespective PC line interconnected between the frame arm and the framecenter) regarding the detecting presence. The frame center (e.g., itsservice processor) may then read (e.g., over the respective I²C line)the memory of the virtual slot to obtain an indication of the fixedlocation of the virtual slot (and thus the installed FRU) within therack, and then utilize the fixed location data to perform one or moreOOB management tasks with respect to the newly installed FRU. Forinstance, the frame manager may maintain or at least have access to(e.g., within a memory of the frame center) various types of informationin relation to minimum processing and storage capacities of installedFRUs, power and cooling requirements, physical locations, currentfirmware version, network connections, and the like, all of which may beused as part of the OOB management of the FRU.

In this regard, part of the OOB management performed by the framemanager may include obtaining one or more properties from the OOBservice processor of a newly installed FRU and comparing such propertiesto minimum or expected properties. Upon the frame manager determiningthat the FRU includes the expected properties or otherwise validatingthe FRU, the frame manager may then instruct the main processor on themotherboard of the FRU to power up (e.g., via establishing a connectionwith the OOB service processor of the FRU (e.g., over the respectiveEthernet cable interconnected between the frame center and the framearm)) so that the FRU can proceed to operate in any appropriate manner.Thereafter, the UMS portion on the OOB service processor of the FRU maysend alerts or messages to the frame manager via the communicationspath(s) (e.g., a network cable) as appropriate in relation to faults,FRU hot-swapping requests, and the like. Among other advantages, a rackor cabinet including the disclosed frame or system installed therein mayhold data center floor space for later, rapid deployment of varioustypes of FRUs (e.g., in response to service demand, roll-out of newservices, and/or the like).

In one aspect, a storage rack for supporting electronic devices (e.g.,FRU) includes a plurality of front vertical support pillars, a pluralityof rear vertical support pillars that are spaced from the plurality offront support pillars, a plurality of pairs of first rail assembliesrigidly interconnecting the plurality of front and rear vertical supportpillars, and a plurality of first housings. Each first housing rigidlyinterconnects a first rail assembly of a respective one of the pluralityof pairs of first rail assemblies to an opposite second rail assembly ofthe respective one of the plurality of pairs of first rail assemblies,and each first housing includes one or more first blind mate connectorsfixable thereto.

In one arrangement, each first housing may include a pair of sidemembers, where a first side member of the pair of side members of thefirst housing is rigidly interfaceable with the first rail assembly ofthe respective one of the plurality of pairs of first rail assemblies,and where a second side member of the pair of side members of the firsthousing is rigidly interfaceable with the second rail assembly of therespective one of the plurality of pairs of first rail assemblies. Eachfirst housing may also include an attachment portion rigidlyinterconnecting the first and second side members of the first housing,where the attachment portion rigidly supports the one or more firstblind mate connectors of the first housing. For instance, the attachmentportion may include a tray including first and second opposite ends andtop and bottom surfaces between the first and second ends, where thefirst end of the tray of the first housing is attached to the first sidemember of the first housing and the second end of the tray of the firsthousing is attached to the second side member of the first housing. Theattachment portion may also include a wall protruding from top surfaceof the tray of the first housing, where the one or more first blind mateconnectors extend through the wall of the first housing.

In another arrangement, the storage rack may include a plurality ofpairs of second rail assemblies that are slidably engageable withrespective ones of the plurality of pairs of first rail assemblies, anda plurality of second housings that each rigidly interconnect a firstrail assembly of a respective one of the plurality of pairs of secondrail assemblies to an opposite second rail assembly of the respectiveone of the plurality of pairs of second rail assemblies. Each secondhousing is configured to engage with a respective one of the pluralityof first housings when a corresponding one of the plurality of pairs ofsecond rail assemblies slidably engages with a respective one of theplurality of pairs of first rail assemblies.

For instance, each second housing may include one or more second blindmate connectors fixable thereto that electrically connect with the oneor more first blind mate connectors when the respective one of theplurality of pairs of second rail assemblies slidably engages with therespective one of the plurality of pairs of first rail assemblies. Eachof a plurality of FRUs may be rigidly connected to the first and secondrail assemblies of respective ones of the plurality of pairs of secondrail assemblies, where each FRU is electrically connected to the one ormore second blind mate connectors of the one of the second housings thatis rigidly interconnected to the first and second rail assemblies of therespective one of the plurality of pairs of second rail assemblies. Theelectrical connection between the one or more second blind mateconnectors and the one or more first blind mate connectors electricallyconnects the FRU with a central management controller of the storagerack.

In another aspect, a node of a backplane of a storage rack for computingdevices is disclosed that is configured to be mounted adjacent a rear ofa bay of the storage rack and electrically interconnect with a computingdevice received in the bay. The disclosed node includes a housingincluding a pair of side members and an attachment portion rigidlyinterconnecting the first and second side members, where the housing isconfigured to rigidly interconnect first and second rail assembliesdefining the bay in the storage rack. The attachment portion includes atray including first and second opposite ends and top and bottomsurfaces between the first and second ends, where the first end of thetray is attached to the first side member and the second end of the trayis attached to the second side member. The attachment portion alsoincludes a wall protruding from top surface of the tray, where one ormore blind mate connectors extend through the wall of the first housing.

In one arrangement, a first of the one or more blind mate connectors isslidably receivable between first and second guide members of the trayand into the wall of the first housing. Additionally or alternatively,the wall may include a first alignment slot extending along a firstlongitudinal axis and a second alignment slot extending along a secondlongitudinal axis that is perpendicular to the first longitudinal axis,where the first of the one or more blind mate connectors includes firstand second spaced alignment pins that are slidably receivable in thefirst and second spaced alignment slots.

In a further aspect, a method is disclosed for adapting a storage rackto facilitate out of band (OOB) management of field replaceable units(FRUs) mounted within the storage rack by a central managementcontroller connected to the computing rack. The method includes mountinga plurality of pairs of first rail assemblies to front and rear verticalsupport pillars of the storage rack, and rigidly securing one of aplurality of housings to first and second rail assemblies of each pairof first rail assemblies. Each housing includes a circuit boardcomprising a memory storing data indicating a location of the housingrelative to other ones of the plurality of housings of the storage rack,and a connector electrically interconnected to the circuit board andconfigured to interface with a corresponding connector of a FRU to allowfor OOB management of the FRU by the central management controller.

Any of the embodiments, arrangements, or the like discussed herein maybe used (either alone or in combination with other embodiments,arrangement, or the like) with any of the disclosed aspects. Merelyintroducing a feature in accordance with commonly accepted antecedentbasis practice does not limit the corresponding feature to the singular.Any failure to use phrases such as “at least one” does not limit thecorresponding feature to the singular. Use of the phrase “at leastgenerally,” “at least partially,” “substantially” or the like inrelation to a particular feature encompasses the correspondingcharacteristic and insubstantial variations thereof. Furthermore, areference of a feature in conjunction with the phrase “in oneembodiment” does not limit the use of the feature to a singleembodiment.

In addition to the exemplary aspects and embodiments described above,further aspects and embodiments will become apparent by reference to thedrawings and by study of the following descriptions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates one embodiment of a setup including a smart computingframe or system installed within a computing rack for facilitating outof band management of a plurality of FRUs within the rack, such asrack-mounted servers, backup power modules, and/or the like.

FIG. 2 is a schematic diagram of a system designed to accept an ACand/or DC input power supply and distribute redundant DC voltages toeach of a plurality of FRUs mounted within a computing rack, accordingto an embodiment.

FIG. 3a is a schematic diagram of one configuration of the system ofFIG. 2 that is designed to accept an AC input power source.

FIG. 3b is a schematic diagram of another configuration of the system ofFIG. 2 that is designed to accept a DC input power source.

FIG. 3c is a schematic diagram of a further configuration of the systemof FIG. 2 that is designed to accept both AC and DC input power sources.

FIG. 4 is a more detailed schematic view of a frame arm of the frame ofFIG. 1 about to interface with a corresponding FRU.

FIG. 5 is a more detailed schematic view of a frame center of the frameof FIG. 1.

FIG. 6 is a representative sequence of events that may occur in thecontext of OOB management of FRUs within the frame of FIG. 1.

FIG. 7 is a flow diagram of a method for use of worker and manager PROMimages stored in the frame of FIG. 1 to manage FRUs of a smart computingframe.

FIG. 8 is a schematic diagram of a worker PROM image of the frame ofFIG. 1.

FIG. 9 is a schematic diagram of a manager PROM image of the frame ofFIG. 1.

FIG. 10 illustrates another embodiment of the smart computing frame ofFIG. 1.

FIG. 11 illustrates another embodiment where at least two of the smartcomputing frames of FIG. 1 are interconnected to form a smart computingframe system.

FIG. 12 is a rear perspective view of one example of the smart computingframe of FIG. 1.

FIG. 13 is a perspective view of a frame arm of the frame of FIG. 12.

FIG. 14 is a perspective view of an adapter that may be used tointerface a FRU with a frame arm of the frame of FIG. 12.

FIG. 15 is a perspective view of the adapter of FIG. 14 secured onto aside of a FRU.

FIG. 16 is another perspective view illustrating how the adapter of FIG.14 facilitates electrical connections between various ports of the FRUand a blind mate connector.

FIG. 17 is a close up perspective view of a rear portion of the blindmate connector of FIG. 16.

FIG. 18 is a side view of the FRU of FIG. 16 being received in areceiving bay of the frame of FIG. 12 before the blind mate connector ofthe adapter has interfaced with a corresponding blind mate connector ofthe frame arm of FIG. 13.

FIG. 19 is a side view similar to that in FIG. 18, but after the blindmate connector of the adapter has interfaced with the correspondingblind mate connector of the frame arm of FIG. 13.

FIG. 20 is a flow diagram of a method of electrically interfacing a FRUwith a computing rack during insertion of the FRU into a receiving bayof the computing rack.

FIG. 21 is a perspective view of an adapter and corresponding frame armaccording to another embodiment.

FIG. 22 is another perspective view the adapter and frame arm of FIG.21.

FIG. 23 is another perspective view of the frame arm of FIG. 21.

FIG. 24 is a rear perspective view of another example of the smartcomputing frame of FIG. 1.

FIG. 25 is a perspective view of a frame backplane node being blind mateconnected to a FRU adapter of the frame of FIG. 24.

FIG. 26 is a close-up perspective view of a rail assembly rigidlyinterconnecting front and rear vertical pillars of the frame of FIG. 24.

FIG. 27 is a perspective view similar to FIG. 25 but with cover membersbeing removed from the frame backplane node and FRU adapter.

FIG. 28a is an exploded perspective view of the frame backplane node ofFIG. 25.

FIG. 28b is a front view of the frame backplane node of FIG. 25.

FIG. 29 is a close-up perspective view of a portion of the housing ofthe frame backplane node of FIG. 25 and illustrating first and secondalignment slots in the housing for receiving first and second alignmentpins of a blind mate adapter.

FIG. 30 is a plan view of frame backplane node of FIG. 27.

FIG. 31 is a first perspective view of the frame backplane node of FIG.25.

FIG. 32 is a second perspective view of the frame backplane node of FIG.25.

FIG. 33 is an exploded perspective view of the FRU adapter of FIG. 25.

FIG. 34 is a plan view of FRU adapter of FIG. 27.

FIG. 35 is a first perspective view of the FRU adapter of FIG. 25.

FIG. 36 is a second perspective view of the FRU adapter of FIG. 25.

FIG. 37 is a partial exploded perspective view of the frame backplanenode and FRU adapter of FIG. 25.

DETAILED DESCRIPTION

Disclosed herein are systems and methods for the central management of aplurality of rack-mounted FRUs (e.g., servers, backup power modules,and/or the like) that provide levels of availability and serviceabilitysimilar to those provided within chassis or blade-based systems but freeof many of the inherent restrictions of blade-based systems. Broadly,the disclosed system includes a plurality of “frame backplane nodes,”“virtual slots” or “frame arms” (e.g., receiving structures, housings,connectors, and/or the like) for electrically interconnecting with acorresponding plurality of FRUs (e.g., having similar or disparate formfactors and functionalities). For instance, adjacent frame arms may beappropriately spaced along the height or other dimension of a computingrack or cabinet (e.g., such as by 1U or multiples thereof) and may beconveniently aligned with slide rails and/or other mounting features sothat a FRU inserted into the rack via the slide rails or other mountingfeatures may be operable to automatically interconnect with a respectiveframe arm.

The disclosed system may also include a “frame center” (e.g., “framemanagement module,” “central management controller,” “central managementmodule,” “central computing device,” etc.) that is electricallyinterconnectable to each of the virtual slots by a “fixed interconnecttopology” in a manner that allows for FRU presence detection (i.e.,detection of a FRU in one of the receiving bays at a known, fixedlocation within the rack), FRU OOB management (e.g., in relation tostart-up, hot-swapping, power and cooling monitoring, and/or the likevia a “frame manager” implemented in and/or in communication with theframe center), and the like. The system (including the frame arms, framecenter, and fixed interconnect topology) may be incorporated into therack or cabinet as part of building the rack or else be retrofitted orotherwise integrated into an existing rack (i.e., an existing rack thathas not been purpose-built specifically for the system). That is, therack/cabinet and FRUs may be standalone products that are independent ofthe system. The combination of the system/frame and a rack or cabinetmay collectively form a “setup.”

As used herein, the term “fixed interconnect topology” connotes aplurality of communication paths/lines/cables (e.g., those necessary forFRU presence and fixed location detection, OOB management, etc.) fixedlyconnecting the frame center to each of the plurality of frame arms. Theplurality of communication lines may include a plurality of I²C cables,each of which is electrically interconnected between the frame centerand a respective one of the frame arms. The plurality of communicationlines may also include a plurality of Ethernet cables, each of which iselectrically interconnected between the frame center and a respectiveone of the frame arms. The fixed interconnect topology may also includea plurality of power paths/lines/cables fixedly interconnecting each ofone or more PDUs to each of the plurality of frame arms and/or directlyto each of a plurality of installed FRUs. Each of the communication andpower paths or lines includes two endpoints, where the first endpoint(e.g., endpoint “A”) is connected to a particular port of the framecenter or PDU and where the second endpoint (e.g., endpoint “B”) isconnected to a particular frame arm (e.g., where the frame arm is at anoffset U within the frame).

Turning now to FIG. 1, a schematic side view of a computing frame orsystem 100 is disclosed that allows rack-type FRUs (e.g., rack-mountservers, backup power modules, and the like) to be managed in a mannersimilar to that in which blade-type servers are managed within a bladeenclosure or chassis, but in a manner that is largely free of many ofthe inherent limitations of blade-type systems. The frame 100 may besecured to or otherwise implemented within any appropriate rack orcabinet 104 having a plurality of bays or receiving locations (not shownin FIG. 1) sized to receive a respective plurality of FRUs 112 of one ormore types and/or form factors such as rack-mount servers, bladeenclosures (each holding one or more blade servers), and/or otherelectronic devices in a stacked or overlapping fashion. The rack 104 mayinclude any appropriate number of posts or vertical support members orrails 108 (e.g., two, four, and the like) based upon the particularenvironment in which the frame 100 is to be implemented. Associated withthe posts 108 may be a series of slide rails, rail assemblies, or otherstructures (not shown) that allow the FRUs 112 to be selectivelyinserted into and secured to the rack 104. The posts 108 may beappropriately secured to the floor or other adjacent building structureto limit the frame 100 from falling over. Other details concerning therack 104 (e.g., panels, fasteners, and the like), how the FRUs 112 areinserted into and removed from the rack 104, and the like will not befurther discussed in relation to FIG. 1 in the interest of clarityand/or brevity.

The frame 100 includes a plurality of frame arms 116 (e.g., virtualslots, receiving structures, etc.), each of which is configured toelectrically interface with a corresponding one of a plurality of theFRUs 112 (e.g., via respective corresponding connectors 128, 132 as willbe discussed in more detail below). The frame 100 also includes a framecenter 120 (e.g., a separate, dedicated computing device) implementing aframe manager 168 (e.g., software, logic) or otherwise working at thedirection of the frame manager 168 (e.g., in the case where the framemanager 168 is implemented on another device) for receiving FRUinsertion/removal alerts from the frame arms 116 and performing OOBmanagement of the FRUs 112. While the frame manager 168 has beenillustrated as being implemented within the frame center 120, somearrangements envision that some or all of the frame manager 168 may beimplemented on a device separate from but in communication with theframe center 120 (e.g., an installed FRU 112, a device separate from theframe center 120 and FRUs 112, and/or the like).

A fixed interconnect topology 124 (e.g., harness) of communication linesor paths (e.g., wired or wireless) directly interconnects the framecenter 120 to each of the frame arms 116. As discussed previously, theplurality of communication paths may include a plurality of I²C paths(e.g., cables), each of which is electrically interconnected between theframe center 120 and a respective one of the frame arms 116. Each I²Ccable facilitates transmission of alerts from a respective frame arm 116to the frame center 120 regarding FRU presence detection, requests toremove a FRU 112 from a particular receiving bay (e.g., initiated via auser depressing a button on the respective frame arm 116), and/or thelike. The frame center 120 can also utilize an I²C cable to read amemory of a respective frame arm 116 to obtain data indicating a fixedlocation of the frame arm 116 (and thus an interfaced FRU 112) withinthe frame 100 and subsequently utilize the fixed location data as partof performing OOB management of the interfaced FRU 112 (discussed inmore detail below).

The plurality of communication paths of the fixed interconnect topology124 may also include a plurality of network (e.g., Ethernet) paths(e.g., cables) each being electrically interconnected between the framecenter 120 and a respective one of the frame arms 116 and whichcollectively create a local area network (LAN) within the frame 100and/or rack 104. Each network cable may essentially “pass-through” itsrespective frame arm 116 to facilitate substantially directcommunications between the frame center 120 and an OOB service processor164 (e.g., ILOM) of an interfaced FRU 112 for use in performing OOBmanagement of the FRU 112 (e.g., in addition to allowing for network(e.g., Internet, WAN, LAN) communications between the FRU 112 andservers, processes, devices, etc. outside of the frame 100 and/or rack104). In this regard, the frame center 120 may utilize the I²C cables toreceive FRU insertion/removal alerts and to identify one or moreparticular fixed locations within the frame 100 of particular frame arms116 and corresponding FRUs 112 (e.g., via reading the memory of theframe arm 116), and may utilize the network cables to perform OOBmanagement of one or more of the FRUs 112 (e.g., via communicating withthe OOB service processor 164 and/or other management entity of the FRUs112).

For instance, each cable/line may be in the form of“line-endpoint(A):management-server(X):port(N)<->line-endpoint(B):receive-structure(U).”The fixed interconnect topology 124 may also include a plurality ofpower paths/lines/cables fixedly interconnecting each of one or morePDUs 126 to each of the plurality of frame arms 116 (so that a FRU 112may receive power upon the connector 132 of a FRU 112 interfacing withthe corresponding connector 128 of its respective frame arm 116), or, insome arrangements, directly to ports on each of the FRUs 112. In anyevent, the fixed interconnect topology 124 may essentially form at leastpart of a “virtual” backplane or midplane that allows a FRU 112 to beable to substantially seamlessly join whatever management servicecontext it is part of (in this case, the UMS running on the framemanager 168 and OOB service processors 164 of installed FRUs 112).

Before discussing the frame arms 116, frame center 120, FRUs 112, andinteractions therebetween in more detail, reference will now be made toFIG. 2 which illustrates a system 500 for receiving one or both of an ACinput power source (e.g., one or more mains power supplies) and a DCinput power source (e.g., battery banks, AC to DC converters, other DCpower supplies, etc.), and then providing first and second DC voltages(e.g., −48V) to respective first and second DC power distribution units(PDUs) for distributing dual/redundant DC power to FRUs mounted within acomputing rack. While the system 500 will be discussed in conjunctionwith the system 100, it is to be understood that the system 500 may beused to provide power to FRUs mounted within a rack not incorporatingthe system 100.

Generally, current telecommunications systems are required to be able toaccept either an AC power source (e.g., mains electricity) or a DC powersource (e.g., battery banks) for powering equipment (e.g., rack-mountedFRUs) of the systems. In this regard, telecommunications systems oftenhave different sets of equipment (e.g., power converters, rectifiers,PDUs, power cables, etc.) for respectively receiving AC and DC inputpower sources and distributing a voltage to FRUs or other equipment ofthe system. For instance, when a particular computing rack is to receivean AC power supply, the rack will have a first particular set ofequipment designed to accept the AC power supply and eventuallydistribute (e.g., via one or more PDUs) a voltage to each of a pluralityof FRUs. However, when the same computing rack is to receive one or moreDC power supplies, then the rack will have a separate second particularset of equipment designed to accept the one or more DC power suppliesand distribute one or more DC voltages to each of a plurality of FRUs(e.g., via one or more PDUs). Maintaining separate sets of equipment forAC and DC power sources results in increased testing and validationscosts for the manufacturer, operational costs for the manufacturer andend customer, and costs for sparing parts for both sets of equipment.

In this regard, the system 500 disclosed herein includes a single set ofequipment that is designed to accept an input AC and/or DC power sourceand distribute at least one DC voltage to each of a plurality of FRUsmounted within a computing rack (e.g., FRUs 112 of FIG. 1, FRUs of adifferent computing rack, and/or the like) regardless of whether theinput power source is AC and/or DC. As the system 500 includes only asingle set of equipment, numerous reductions in various types of costs(e.g., testing, operational, validation, spare parts) may be realized inrelation to current telecommunications systems. For instance, as NetworkEquipment-Building System (NEBS) certification testing often costs over$100,000 just for initial testing and up to $30,000 for subsequenttests, the cost savings from being able to utilize AC and/or DC powersources with a single set of equipment can be substantial.

As shown in FIG. 2, the system broadly includes an AC to DC converter orrectifier 504, at least first and second DC PDUs 508, 512 (e.g.,rack-mounted PDUs, smart or intelligent PDUs, etc.), and an electricalbypass mechanism 516 electrically connected between the rectifier 504and the first and second DC PDUs 508, 512. The bypass mechanism 516 isconfigured to deliver a DC voltage to each of the first and second DCPDUs 508, 512 from an AC power source (e.g., via the rectifier 504)and/or from a DC power source as will be discussed below. Stateddifferently, the rectifier 504 and bypass mechanism 516 may collectivelybe considered a “power conversion apparatus” that is configured todeliver a DC voltage to each of the first and second DC PDUs 508, 512regardless of whether a power supply inputted to the power conversionapparatus includes one or more AC power sources, one or more DC powersources, or both AC and DC power sources.

The rectifier 504 may broadly include one or more (e.g., a plurality of)input nodes 520 (e.g. ports, contacts, pads) for electrical connectionwith one or more AC power sources or supplies such as one or more mainsinput feeds (e.g., 20A, 200-240V, single or multi-phase, etc.), at leastone output node 524 (e.g., port, contact, pad) for electrical connectionwith so as to pass a DC voltage to the bypass mechanism 516, andcircuitry 528 (e.g., any appropriate arrangement of one or moretransformers, diodes, resistors, and/or the like) configured to convertthe AC power from the AC power source(s) into a DC voltage (e.g., −48V).Each of the first and second DC PDUs 508, 512 may include at least onerespective input node 532, 536 (e.g., port, contact, etc.) forelectrical connection to the bypass mechanism 516, a plurality of outputnodes 540, 544 (e.g., outlets) for electrical connection to the framearms 116 (e.g., to the connectors 128 of the frame arms 116) or directlyto the FRUs 112 or other rack-mounted equipment, and any appropriatecircuitry 546, 550 operable to receive a DC voltage from the bypassmechanism 516 and distribute DC power to FRUs 112 (or other rack-mountedequipment) via the output nodes 540, 544. To provide redundant or backuppower (e.g., redundant power supplies (RPS)) to each of the FRUs 112,respective sets 554 ₁, 554 ₂, 554 ₃, 554 ₄, etc. of power cables/cordsmay be electrically connected between respective output nodes 540, 544of the first and second DC PDUs 508, 512 and each of the frame arms 116,FRUs 112, etc.

For instance, first ends of the first set 554 ₁ of power cables may berespectively plugged into or otherwise electrically connected to firstoutput nodes 540, 544 of the first and second DC PDUs 508, 512 whilesecond ends of the first set 554 ₁ of power cables may both beelectrically connected to the same frame arm 116, the same FRU 112, etc.Each of the first and second DC PDUs 508, 512 may be loaded to somepercentage less than its rated maximum load to avoid tripping itscircuit breaker. In one arrangement, the first and second DC PDUs 508,512 may share the FRU 112 load at about 50% each but with each of thefirst and second DC PDUs 508, 512 being loaded at less than 50% of itsrated maximum load. Thus, even in the event that one of the first andsecond DC PDUs 508, 512 loses power resulting in the other of the firstand second DC PDUs 508, 512 having to support 100% of the load, theremaining PDU will still be loaded less than its rated maximum load.

With continued reference to FIG. 2, the bypass mechanism 516 may includeat least one input node 558 (e.g., contact, junction) for electricalconnection (e.g., via a trace, line, cable) to the output node 524 ofthe rectifier, at least first and second output nodes 562, 566 (e.g.,contacts, pads) for respective electrical connection to the input nodes532, 536 of the first and second DC PDUs 508, 512, a first conductivepath 570 (e.g., trace, line, cable) electrically connecting the inputnode 558 to the first output node 562, and a second conductive path 574(e.g., trace, line, cable) “interruptably electrically connectable”between the input node 558 and the second output node 566. While thesecond conductive path 574 has been shown as extending from the inputnode 558 to the second output node 566, it is to be understood that thesecond conductive path 574 may, in other embodiments, extend from someportion of the first conductive path 570 (e.g., as just one example,from a midpoint of the first conductive path 570 between the input node558 and the first output node 562) to the second output node 566 withoutdeparting from the spirit of the present disclosure.

For purposes of this disclosure, “interruptably electricallyconnectable” means that current flow between the input node 558 and thesecond output node 566 can be selectively interrupted or stopped forreasons that will be discussed below. In one arrangement, the secondconductive path 574 may be removable from the bypass mechanism 516. Forinstance, the second conductive path 574 may be in the form of anelectrical jumper that may be removed to interrupt current flow betweenthe input node 558 and the second output node 566. In anotherarrangement, any appropriate switch or button (e.g., not shown) may bedisposed along second conductive path 574 and actuatable ormanipulatable to selectively interrupt or disallow current flow betweenthe input node 558 and the second output node 566. Other arrangementsare also possible and encompassed within the scope of the presentdisclosure.

The system 500 may be electrically interconnected with at least threedifferent arrangements of input power sources and still provide a DCoutput voltage regardless of the input power source arrangement. Turningnow to FIG. 3a (with the first and second DC PDUs 508, 512 being omittedfor clarity), one configuration of the system 500 is illustrated wherebythe input power source is a plurality of AC or mains input feeds 578respective electrically connected to the plurality of input nodes 520 ofthe rectifier 504. After the circuitry 528 has rectified the mains inputfeeds 578 into a DC voltage, the DC voltage is passed through the outputnode 524 of the rectifier 504 to the input node 558 of the bypassmechanism 516. The DC voltage is then sent along the first and secondconductive paths 570, 574 through the first and second output nodes 562,566 to the first and second DC PDUs 508, 512 for distribution to FRUs ofa computing rack or cabinet. While one end of the second conductive path574 is illustrated as being connected to the input node 558, otherarrangements envision that the end may be connected to some portion ofthe first conductive path 570.

With reference now to FIG. 3b , another configuration is illustratedwhereby the input power source is first and second DC power supplies582, 586 (e.g., each supplying −40V to −60V) respectively electricallyinterconnected via first and second conductive lines 590, 594 (e.g.,cables, cords, etc.) to the first and second output nodes 562, 566 ofthe bypass mechanism 516 to respectively supply DC voltages to the firstand second DC PDUs 508, 512. In this configuration, there is no AC inputpower source, and any current flow between the input node 558 and thesecond output node 566 is interrupted.

In one arrangement, the second conductive path 574 may be removed (e.g.,in the case of a removable jumper) and the first and second conductivelines 590, 594 may be respectively directly connected in any appropriatemanner (e.g., plugs, hard-wiring, etc.) to the first and second outputnodes 562, 566 (e.g., as shown in FIG. 3b ) of the bypass mechanism 516.In another arrangement, the second conductive path 574 may remain withinthe bypass mechanism 516 but a switch or the like (not shown) disposedon the second conductive path 574 may be flipped or manipulated tointerrupt current flow along the second conductive path 574. In thisarrangement, the second conductive line 594 may be connected to thesecond output node 566 or to the second conductive path 574 somewherebetween the switch and the second output node 566 while the firstconductive line 590 may be connected to the first output node 562 or tothe first conductive path 570 (or even to the input node 558). In theevent that the first and/or second conductive lines 590, 594 arerespectively connected to the first and/or second conductive paths 570,574, then the respective junctions between the first conductive path andline 570, 590 and the second conductive path and line 575, 594 may insome cases be considered the first and second output nodes 562, 566. Asthere is no AC input power source in this configuration, the rectifier504 may in some embodiments be omitted (e.g., in those contexts in whichit is not envisioned that an AC input power source would ever beutilized). In one variation, the first conductive path 570 mayadditionally be appropriately interrupted (e.g., via removing the firstconductive path 574, manipulating a switch disposed along the firstconductive path 574, and/or the like).

FIG. 3c illustrates another configuration of the system 500 that isrepresentative of an integrated uninterruptable power supply (UPS)input. In this configuration, current flow between the input node 558and the second output node 566 is again interrupted as discussed abovein relation to FIG. 10b (e.g., via removing the second conductive path574, actuating a button or switch on the second conductive path 574,and/or the like). However, the input power source now includes both anAC input power source and a DC input power source. For instance, one ormore mains input feeds 578 may be respectively electrically connected tothe input nodes 520 of the rectifier 504 so as to supply a DC voltage tothe first DC PDU 508 via the output node 524, input node 558, firstconductive path 570 and first output node 562. Also, a DC power supply598 (e.g., one of first and second DC power supplies 582, 586) may beelectrically connected via conductive line 599 (e.g., one of first andsecond conductive lines 590, 594) to the second output node 566 (or to aportion of the second conductive path 574 between switch (not shown) andthe second output node 566) to supply a DC voltage to the second DC PDU512.

While the rectifier 504, bypass mechanism 516 and first and second DCPDUs 508, 512 have been illustrated in FIGS. 2-3 c as being separatecomponents, one or more of the various components may be integrated intoother of the components. For instance, the rectifier 504 and bypassmechanism 516 (e.g., the power conversion apparatus) may both beimplemented into a single integrated circuit and/or into a commonhousing. As another example, one or more features of the bypassmechanism 516 or rectifier 504 may be implemented into the first and/orsecond DC PDUs 508, 512. In this regard, the diagrams shown in FIGS. 2-3c have merely been presented to illustrate the various functionalitiesof the system 500 rather than necessarily limiting the breadth of thesystem 500. Turning back to FIG. 1, each frame arm 116 generallyconnotes any appropriate arrangement of one or more parts or componentsthat can electrically interface with one or more different types of FRUs112 to allow the FRU 112 to draw power from the PDUs 126 and to allowthe frame center 120 to perform OOB management of the FRU 112. Broadly,each frame arm 116 may include a memory 136 storing data 141 (e.g., oneor more IDs or addresses) indicating a particular fixed or physicallocation of the frame arm 116 within the frame 100 relative to the otherframe arms 116. Each frame arm 116 may also have a connector 128 that isconfigured to mate with a corresponding connector 132 of a respectiveFRU 112 upon insertion of the FRU 112 into a respective receiving bay ofthe rack 104 (associated with the frame arm 116) to allow the FRU 112 todraw power from the PDUs 126 and the frame manager 168 to communicatewith the OOB service processor 164 of the FRU 112 via the fixedinterconnector topology 124 and the respective connectors 128, 132.

FIG. 4 presents a more detailed schematic view of one of the frame arms116 as it is about to interface with a corresponding FRU 112. The framearm 116 may include any appropriate housing 118 to which the connector128 and a circuit board such as printed circuit board (PCB) 122 may besecured. The housing 118 may, for instance, be mounted to the frameworkof the rack 104 adjacent one of the receiving bays of the rack 104(e.g., adjacent a rear portion of the rack 104) so that, upon insertionof the FRU 112 into the receiving bay, the connector 132 (e.g., blindmate connector) of the FRU 112 may electrically interface with theconnector 128 (e.g., corresponding blind mate connector) of acorresponding frame arm 116 (e.g., corresponding pins/contacts of theconnectors 128, 132 may contact or otherwise electrically interface).The PCB 122 may have any appropriate arrangement of circuitry thatincludes the memory 136 storing the location data 141 of the frame arm116 (e.g., where the location data may be included within a “worker”programmable read-only (PROM) image 140 as discussed later on in thisdiscussion).

An I²C data line 20 (e.g., cable, cord, path, etc., part of the fixedinterconnect topology 124, not shown) may be electrically connected atone end to the PCB 122 (e.g., to an I²C data bus of the PCB 122, notshown) and at an opposing end to the frame center 120 (discussed in moredetail below) to allow the frame arm 116 to send alerts to the framecenter 120 (e.g., regarding FRU presence detection, requests to remove aFRU 112 from the receiving bay and thus the OOB management network,and/or the like) as well as to allow the frame center 120 to read thelocation data 141 from the memory 136 (e.g., upon receiving acorresponding alert) to determine configuration information for the FRU112 based on the read location information. The PCB 122 may also includeany appropriate logic 130 (e.g., electrically connected to the I²C databus of the PCB 122) operable to convert between serial data and I²C datafor reasons discussed below, one or more LEDs 180 (or other types ofindicators) that broadly indicate one or more operational states orstatuses of the frame arms 116, and/or one or more buttons 182 or thelike that, when manipulated (e.g., depressed), are operable to cause thegeneration and transmission of a signal or other communication from theframe arm 116 to the frame center 120 (e.g., a request to remove a FRU112 from the frame arm 116 and thus from the management network of theframe 100). For instance, the operational states of a particular framearm 116 indicated by the LEDs 180 may range from an initial state of noFRU 112 being interfaced with the frame arm 116 all the way through to afinal state of one or more FRUs 112 being interfaced and active (e.g.,all manual servicing of the frame 100 is complete). The LEDs 180 mayalso indicate proper transition from initial to final state as well aserror states that may require additional specific recovery operations.

The frame arm 116 also facilitates “pass-through” of a network (e.g.,Ethernet) cable 24 from the frame center 120 to the connector 128 aswell as one or more power cables such as first and second power cables28, 32 (e.g., one of sets 554 ₁-554 ₄ in FIG. 2) from first and secondDC PDUs (e.g., first and second DC PDUs 508, 512 in FIG. 2) to theconnector 128. Stated differently, the network cable 24 and first andsecond power cables 28, 32 need not necessarily communicate or interactwith the PCB 122 and thus may be in substantial direct connection withthe FRU 112 upon interfacing of the connectors 128, 132.

With respect to the FRU 112 (a rear portion of the FRU 112 being shownin FIG. 4), the connector 132 may be non-movably (e.g., rigidly) securedto the FRU 112 (e.g., directly or indirectly) via any appropriatearrangement 134 of brackets, linkages, and/or the like (onerepresentative example of an arrangement 134 will be discussed later onin relation to FIGS. 14-20). A network (e.g., Ethernet) port 36 of theFRU 112 may be electrically connected to the connector 132 by a networkcable 40, and first and/or second power ports 44, 48 of the FRU 112 maybe electrically connected to the connector 132 by respective powercables 52, 56. Furthermore, a serial management port 60 of the FRU 112may be electrically connected to the connector 132 by a serial data line64. In this regard, interfacing of respective pins and/or contacts (notshown) of the connectors 128, 132 automatically allows the FRU 112 todraw power from the PDUs 126 via power cables 28, 52 and/or power cables32, 56, and automatically allows for network communications between theframe manager 168 (and/or frame center 120) and the OOB serviceprocessor (e.g., ILOM) 164 (shown in FIG. 1) of the FRU 112 (as well asnetwork communications between the FRU 112 and devices/processes outsideof the frame 100 and rack 104) via network cables 24, 40.

Also upon interfacing of the connectors 128, 132, a serial dataconnection is established between the serial management port 60 and thePCB 122 via serial data line 64. In this regard, requests from the OOBservice processor 164 of the FRU 112 to read information (e.g., such aslocation data 141, role information, etc.) from the memory 136 of thePCB 122 (via serial management port 60 and serial data line 64) may beconverted into I²C data by logic 130 for use in servicing the request.The requested information may then be converted back into serial data bythe logic 130 before being sent back to and/or received by the OOBservice processor 164 of the FRU 112. It is to be understood that eachof the plurality of frame arms 116 may be substantially similar to theaforementioned frame arm 116 and may differ only in relation to theirfixed location data 141 (i.e., each frame arm will have a different,specific fixed location within the frame 100) and/or the like. However,it is noted that the each of the FRUs 112 that interface with the framearms 116 need not necessarily be the same in terms of form factors,function, and/or the like, so long as such FRUs 112 include a connector132 matable with the connector 128 of one of the frame arms 116, wherethe connector 132 is electrically connected to network, serialmanagement and power ports of the FRUs 112 as discussed above.

Turning now to FIG. 5, a more detailed schematic view of the framecenter 120 is presented. As discussed above, the frame center 120 may bea stand-alone, separate, dedicated computing device that facilitates OOBmanagement by the frame manager 168 of what may be a plurality ofdisparate FRUs 112 mounted within a common computing rack 104 in amanner similar to how blades are managed within a blade chassis, butwithout many of the limitations inherently presented by blades (e.g.,such as the necessity that all the blades have common form factors,common functionalities, and the like). In this regard, the frame center120 generally includes a housing 121 including a management controlleror service processor module 160 (e.g., including a processor, on-boardmemory, etc., not shown) designed to work in conjunction with the framemanager 168 to perform OOB management of the FRUs 112. The frame center120 also includes a plurality of interfaces 123 for electricalconnection to each of the plurality of frame arms 116 and PDUs 126through the fixed interconnect topology 124 for use in FRUinsertion/removal detection, OOB management, and the like.

For instance, the interfaces 123 may include a plurality of I²Cinterfaces 127 such as a plurality of general purpose input/output(GPIO) pins disposed on one or more bus expanders, where each of the I²Cinterfaces 127 is electrically interconnectable to the PCB 122 of arespective frame arm 116 through a respective I²C data line 20 of theinterconnect topology 124 (see FIG. 2). The I²C interfaces 127 may formpart of or otherwise be electrically interconnected to an I²C bus (notshown) that electrically connects the I²C interfaces 127 to the serviceprocessor 160. The interfaces 123 may also include a plurality ofnetwork interfaces 129 such as a plurality of Ethernet ports of anetwork switch that is electrically connected to the service processor160 in any appropriate manner. Each network interface 129 iselectrically interconnectable to the connector 128 of a respective framearm 116 through a respective network line 24 of the interconnecttopology 124 (see FIG. 4).

The frame center 120 also includes (or at least has access to) a memory144 storing both fixed location data 141 of the frame center 120 withinthe frame 100 (i.e., a location of the frame center 120 relative to theframe arms 116 within the frame 100) as well as fixed interconnecttopology information 145. Broadly, the topology information 145 includesa definition of an expected overall topology of the frame 100 includingthe fixed location data 141 of each of the frame arms 116, IP addressesof each of the frame arms 116, which of the I²C interfaces 127 issupposed to be electrically connected to which of the frame arms 116(e.g., where each frame arm 116 may be identified by its respectivefixed location data), which of the network interfaces 129 is supposed tobe electrically connected to which of the frame arms 116, and/or thelike. The topology information 145 also includes configuration recordsfor the various frame arms 116 and the FRUs 112 respectively interfacedwith the frame arms 116. For instance, the configuration records mayinclude information such as types of FRUs 112 that may be respectivelyinterfaced with particular ones of the frame arms 116, power and coolingrequirements of particular FRUs 112, and/or the like. The fixed locationdata 141 and topology information 145 may be respectively stored withinworker and manager PROM images 140, 148 as will be discussed later onthis disclosure.

In one arrangement, the frame center 120 may also include a plurality ofindicators 175 such as one or more LEDs 175 that are electricallyinterconnected to the I²C interfaces 127 (e.g., to the I²C data bus) andthat are configured to activate (e.g., turn on, blink, etc.) based onone or more states or statuses of one or more of the FRUs 112 (e.g.,faults, requests to remove, etc.). In any event, users can flexiblycustomize the overall topology of the frame 100 (i.e., modify the“virtual backplane”) by simply implementing changes to the information145 (e.g., associating a particular frame arm 116 with a different oneof the interfaces 123 of the frame center 120 via any appropriate userinterface in communication with the frame center 120) and/or the fixedinterconnect topology 124 (e.g., removing one end of a particularnetwork line 24 from one of the network interfaces 127 and plugging itinto a different one of the network interfaces 127). The ability toflexibly customize the overall topology of the frame is in contrast tothe backplanes of blade enclosures which are fixed/static and generallyunable to be modified.

In another arrangement, the service processor 160 of the frame center120 may be able to verify whether the various connections between theframe center 120 and the frame arms 116 via the fixed interconnecttopology 124 match the expected topology definitions stored in thetopology information 145 in the memory 144 of the frame center 120. Forinstance, the service processor 160 may be able to confirm whether firstand second ends of a particular I²C line 20 are respectivelyelectrically connected to the particular I²C interface 127 and frame arm116 specified in the topology information 145. With reference to FIGS.1, 4 and 5, the service processor 160 of the frame center 120 mayinitially read the topology information 145 in the memory 144 to obtaintopology definitions for the frame center 120, the frame arms 116, andthe fixed interconnect topology 124. For instance, the topologydefinitions could specify that a first I²C interface 127 of the framecenter 120 is supposed to be electrically connected to a first frame arm116 (as identified by its respective ID or location information 141) bya first I²C line 20, a second I²C interface 127 of the frame center 120is supposed to be electrically connected to a second frame arm 116 by asecond I²C line 20, and so on. The topology definitions could specifysimilar information for the various network lines 24 and/or other powerand communication channels of the fixed interconnect topology 124.

The service processor 160 may then ascertain whether each of theplurality of communication lines (e.g., the various I²C and networklines 20, 24) of the fixed interconnect topology 124 is electricallyinterconnected between the frame center 120 and one of the plurality offrame arms 116 according to the read topology. In one embodiment, theservice processor 160 may send a plurality of signals over the pluralityof communication lines (e.g., using IP addresses and the like of framearms 116), and then receipt of each of the plurality of signals by theone of the plurality of frame arms 116 respectively associated with theone of the plurality of communication lines in the read physicaltopology may be verified in any appropriate manner. Stated differently,the service processor 160 may send a signal over the particular I²C line20 that is supposed to be electrically connected to frame arm 116 “#3,”and then receipt of the signal by frame arm 116 #3 may be verified. Asimilar process may be performed with each of the various other I²C andnetwork lines 20, 24.

As an example, assume the frame arms 116 are arranged in a particularorientation within the rack 104. For instance, FIG. 1 illustrates howthe frame arms 116 may be generally arranged in a vertically stackedmanner between top and bottom portions of the rack 104 (e.g., where eachframe arm 116 is respectively physically located in a particular orderwithin the rack 104, such as a function of distance from a top or bottomof the rack 104). In this regard, the service processor 160 maysuccessively send each signal over each respective communication linethat is expected to be electrically connected with a particular framearm 116 in a particular order that matches the arrangement of the framearms 116 in the rack 104. Successive receipt of the signals in theparticular order may then be confirmed to quickly verify accurate wiringof the frame 100.

For instance, each successive signal may be configured to activate anindicator (e.g., LED 180) on each respective frame arm 116. In thisregard, proper wiring of the frame 100 may be verified by a userobserving a “visual walking” of the LEDs 180 from the top towards thebottom of the rack 104 (or vice versa). Any miswirings between theactual electrical connections and the expected electrical connectionscould be identified through a skip or inaccuracy in the successivewalking or activation of the LEDs 180 of the frame arms 116. As anotherexample, the service processor 160 may be configured to read thetopology information 145 (of FIG. 5) to determine a particular order ofI²C lines 20 expected to be electrically connected to a particular orderof frame arms 116 (e.g., from the top portion towards the bottom portionof the rack 104), read the location data 141 in the memories of theframe arms 116 via the particular order of I²C lines 20, and then verifythat the read location data 141 matches the location data in thetopology information 145 associated with each of the I²C lines 20. Inone arrangement, any appropriate indicators 175 (e.g., LEDs 177) on theframe center 120 may be configured to illuminate or otherwise activatedepending on whether or not the frame is correctly wired. In response toa miswiring, the frame could be assessed, rewired, and then retested toverify correction wiring.

In this regard, the frame 100 persistently stores information sufficientto allow a connected/interfaced FRU 112 and the frame center 120 toagree on the FRU's 112 physical location within the frame (e.g., inrelation to an offset U). Such persistently stored information may beresident within the frame arms 116, the frame center 120, the fixedinterconnect topology 124, and/or other appropriate location. Forinstance, the topology information 145 in the memory 144 of the framecenter 120 may include a fixed list of all lines/paths of the fixedinterconnect topology 124 in the form of“line-endpoint(A):management-server(X):port(N)<->line-endpoint(B):receive-structure(U).”

In any event, the service processor 160 and/or frame manager 168utilizes the fixed interconnect topology 124 and the frame arms 116 toreadily perform OOB management of FRUs 112 interfaced with the framearms 116 (e.g., regardless of the manufacturer of the FRU 112, the formfactors of the FRU 112, and the like). That is, the frame 100 allows theservice processor 160 and/or frame manager 168 to substantiallyseamlessly perform OOB management of what may be numerous disparatetypes of FRUs 112 installed within the cabinet 104 (e.g., in relation toproduct type, motherboard revision, processor configuration, memoryconfiguration, PCI root and leaf node configuration, and/or the like)but similar to the manner in which the system controller of a bladechassis manages individual blades. With knowledge of the physical orfixed locations of FRUs 112 within the frame 100, the service processor160 and/or frame manager 168 can readily pass communications andrequests to and between the FRUs 112; administrators can readily swapout or otherwise rectify malfunctioning FRUs 112 so as to maintain highlevels of uptime, redundant fault architectures, and low mean time torepair; and the like. In one arrangement, the service processor 160and/or frame manager 168 may be able to monitor for power draws todetermine frame arm 116 and corresponding FRU 112 locations. Forinstance, upon the connector 132 of a FRU 112 being interfaced with acorresponding connector 128 of a particular frame arm 116, the serviceprocessor and/or frame manager 168 may be designed to detect theresultant draw in power by the FRU 112 and thereby determine the FRU's112 fixed or physical location within the frame 100.

Turning now to FIG. 6, one representative sequence 600 of events will bediscussed in the context of OOB management of FRUs 112 within the frame100. At 604, a signal may be received at the frame center 120 from oneof the frame arms 116 regarding a FRU 112 electrically interfaced withthe frame arm 116. As one example, imagine the FRU 112 is installed intothe frame 100 so that its connector 132 interconnects/interfaces withthe corresponding connector 128 of the frame arm 116 (e.g., as in FIGS.1 and 4), where the interfacing between the connectors 128, 132 triggerstransmission of the signal from the frame arm 116 to the serviceprocessor 160 of the frame center 120. For instance, any appropriatecircuitry of the frame arm 116 that is electrically connected to theconnector 128 (e.g., circuitry of the PCB 122, not shown) may detect apower draw by the FRU 112 (e.g., via power ports 44, 48 and power lines52, 56, 28, 32 in FIG. 4) and then generate and send an interrupt oralert to the service processor 160 of the frame center 120 (e.g., overan interrupt line electrically connected between the frame arm 116 andthe frame center 120, over the respective I²C data line 20 electricallyconnected between the frame arm 116 and the frame center 120, and/or thelike). As another example, imagine a user desires to remove a FRU 112from a receiving bay of the rack 104 to perform service on the FRU 112,replace the FRU 112 with another FRU 112 (e.g., hot-swap the FRU 112),and/or the like. For instance, the user may depress a button 182 on theframe arm 116 (e.g., see FIG. 4) to cause the generation andtransmission of a “request to remove” signal/alert (e.g., by anyappropriate logic/circuitry of the PCB 122, not shown) to the framecenter 120.

In response to the received signal, the service processor 160 of theframe center 120 may proceed to ascertain 608 an ID (e.g., address,code, etc.) of the frame arm 116 from which the signal was received inany appropriate manner, where the ascertained ID distinguishes the framearm 116 from other frame arms 116 in the frame 100. For instance, the IDmay identify a fixed location of the frame arm 116 within the frame 100,may be a unique number that identifies the frame arm 116 relative toother frame arms 116, and/or the like. In one arrangement, the serviceprocessor 160 may utilize an ID of the particular interface 123 throughwhich the signal was received as a key into a table or the like ofinterface IDs and corresponding frame arm IDs in the stored topologyinformation 145 (see FIG. 3) to ascertain the frame arm ID. In anotherarrangement, the particular line/cable (e.g., the I²C data line 20) overwhich the signal was received may be a smart or intelligent cableincluding a memory storing any appropriate ID (e.g., serial number orother identification data) that may be read by the service processor 160for use in determining the ID of the frame arm 116. For instance, theservice processor 160 may utilize the ID of the smart cable as a keyinto a table or the like of smart cable IDs and frame arm IDs in thestored topology information 145 to ascertain the frame arm ID.

Using the ascertained frame arm ID as a key, the service processor 160may obtain 612 any appropriate OOB management records corresponding tothe frame arm 116 from the topology information 145 in the memory 144 ofthe frame center 120 and manage 614 the FRU 112 using the obtainedmanagement records. For example, the service processor 160 and/or framemanager 168 may utilize the obtained records to establish a connectionwith the OOB service processor 164 of the FRU 112 over the correspondingnetwork line 129 electrically connected between the frame center 120 andthe frame arm 116 and determine whether or not the FRU 112 meets orsatisfies any particular OOB management requirements of the frame 100(e.g., minimum processing requirements and/or storage capacity, anyparticular motherboard revision number, and/or the like, some or all ofwhich may be policy driven).

As shown in FIG. 6, the managing 614 may include determining 616 one ormore properties of the FRU 112 (e.g., communicating with the OOB serviceprocessor 164 of the FRU 112 to obtain the processing speed of the FRU112, storage capacity, etc.), evaluating 620 the obtained managementrecords in relation to the one or more properties of the FRU 112 (e.g.,determining whether or not the FRU meets any specified minimumprocessing speed, storage capacity, etc.), and taking 624 action basedon the evaluating 620.

For instance, upon determining that the FRU 112 has not met one or moreminimum requirements, the service processor 160 and/or frame manger 168may disallow the FRU 112 from joining the management service context ofthe frame 100 (e.g., and thus not allow the FRU's 112 main processor toeven power up; or only allow the FRU 112 to proceed normally, that is,as if the FRU 112 was not part of the frame 100). Upon validating theFRU 112, however (e.g., determining that the FRU has met any necessarymanagement requirements), the service processor 160 and/or frame manager168 may instruct (e.g., via the OOB service processor 164) the mainprocessor on the motherboard of the FRU 112 to power up so that the FRU112 can proceed to operate as part of the management service context ofthe frame 100 (discussed more fully below).

In addition to FRU insertion alerts, the frame center 120 may alsoreceive alerts or messages from frame arms 116 in relation to faultconditions, requests to remove FRUs 112, and/or the like, and takeappropriate actions. For instance, upon the service processor 160 of theframe center 120 receiving an alert or other message indicative of afault condition(s) from the OOB service processor 164 of a FRU 112(e.g., over the respective network line 24 electrically connecting theframe center 120 to the frame arm 116 to which the FRU 112 is interfacedwith), the frame manager 168 may take any appropriate remedial actionsuch as attempting to rectify the fault, sending an alert to anadministrator indicating the location in the frame 100 of the faulty FRU112, offlining the FRU 112, and/or the like.

As another example, in the event that a user desires to disconnect a FRU112 from its respective frame arm 116 (e.g., as part of a hot-swappingoperation), the user may, as discussed previously, depress a particularbutton 182 on the frame arm 116 (see FIG. 4) to initiate the sending ofa hot-swap request from the frame arm 116 to the service processor 160of the frame center. Upon receiving the hot-swap request, the serviceprocessor 160 may proceed to determine whether hot-swapping of thecorresponding FRU 112 is allowed. For instance, a table of hot-swappingpolicies (or other management policies) for the various frame arms 116and/or corresponding FRUs 112 (e.g., according to frame arm ID such aslocation data) may be maintained in the topology information 155 in thememory 144 of the frame center 120. The service processor 160 may thenproceed to allow or not allow the requested hot-swapping operation basedupon whether or not hot-swapping of FRUs 112 installed in the particularframe arm 116 is or is not allowed. In one arrangement, one or more LEDs180 of a particular color on the frame arm 116 (e.g., see FIG. 2) may beilluminated based on whether or not the requested hot-swapping operationis allowed. Numerous other examples of out of band management by theservice processor 160 and/or frame manager 168 are envisioned andencompassed within the scope of the present disclosure.

In one arrangement, a framework of management record specificationsstored within programmable read-only memory (PROM) images at the framecenter 120 and each of the frame arms 116 may be provided and accessedby the service processor 160 and/or frame manager 168 to determinelocations of frame arms 116 and corresponding FRUs 112, administermanagement policies corresponding to particular FRUs 112, and the like.As will be discussed, the disclosed management record specification maybe implemented within a “manager” PROM image 148 stored in the memory144 at the frame center 120 (and that may be accessed by the serviceprocessor 160 and/or frame manager 168 as part of managing installedFRUs 112) as well as within a plurality of “worker” PROM images 140stored within the memories 136 of the plurality of frame arms 116 andthe memory 144 of the frame center 120 and that may be accessed by theservice processor 160 and/or frame manager 168 to perform OOB managementand by installed FRUs 112 to determine frame roles, physical locations,and the like.

Generally, installing a FRU 112 into a frame arm 116 causes the OOBservice processor 164 of the FRU 112 to access records (e.g., thelocation data 141 of FIG. 2) in a worker PROM image 140 of the frame arm116 to initially determine whether the FRU 112 is installed in the frame100 as opposed to another type of enclosure. Assuming the OOB serviceprocessor 164 is able to read the location records of the worker PROMimage 140, it may then obtain information that both defines its locationwithin the frame 100 as well as its role within the frame (e.g., whetherthe FRU is to function as merely a “worker” FRU, is to take some sort ofmanagerial role within the frame 100, and/or the like). Additionally,the service processor 160 and/or frame manager 168 obtains informationfrom the manager PROM image 148 (e.g., the topology information 145) tounderstand how to manage each of the various FRUs 112 (e.g., in relationto hot-swapping, propagating firmware updates, and the like) in additionto causing updates to the manager PROM image 148 to include recordscorresponding to newly installed FRUs 112. As product and configurationchanges generally only require modification to the manager PROM image148 as opposed to the plurality of worker PROM images 140, the disclosedmanagement record specification can advantageously remain largely staticacross different frame configurations to reduce management overhead.

With reference back to FIG. 4, the memory 136 of each frame arm 116 maybe in the form of a PROM storing the at least one corresponding workerPROM image 140 that contains the fixed location data 141 of therespective frame arm 116. Each worker PROM image 140 includesinformation records that may broadly be used by a FRU 112 to determinewhether the FRU 112 is installed in the frame 100 (i.e., as opposed toanother type of rack or cabinet), determine the FRU's 112 locationwithin the frame 100 (e.g., via the fixed location data 141), determinea particular “role” that the FRU 112 is to assume within the frame 100,allow the FRU 112 to obtain one or more IP addresses for communicatingwith the service processor 160 and/or frame manager 168, and the like(discussed below). Further, the memory 144 of the frame center 120 maybe in the form of a PROM storing the at least one manager PROM image 148that includes the topology information 145 (i.e., the informationnecessary to define the frame 100; e.g., in relation to frame armlocations, configurations, power and cooling requirements, and the like)and which can be used by the service processor 160 and/or frame manager168 to perform OOB management of FRUs 112, route incoming and outgoingcommunications between frame arms 116, and the like. The memory 144 ofthe frame center 120 also stores a corresponding worker PROM image 140that can be used by the frame center 120 to determine its locationwithin the frame 100, determine IP addresses of FRUs for routingmanagement communications, and/or the like.

To further facilitate the reader's understanding of how the FRUs 112,frame arms 116, and the frame center 120 interact within the frame 100to provide the aforementioned increased levels of availability andserviceability, additional reference will now be made to FIG. 7 whichillustrates a method 200 for use with the frame 100 as well as FIGS. 8-9which illustrate schematic diagrams of the worker and manager PROMimages 140, 148 for use within the frame 100. The method 200 may includeinterfacing 204 a FRU 112 with a frame arm 116 of the frame 100. Forinstance, the interfacing 204 may entail inserting a first FRU 152 intoa particular bay of the cabinet 104 so that the connector 132 of thefirst FRU 152 interfaces or otherwise interconnects with the connector128 of a first frame arm 156 (see FIG. 1). The method 200 may theninclude attempting 208 (e.g., by the OOB service processor 164 of thefirst FRU 152) to read a location record (e.g., location data 141 inFIG. 4) of the worker PROM image 140 of the first frame arm 156.

With brief reference to FIG. 8, the worker PROM 140 may include alocation record 304 and a subnet IP record 324. The location record 304may include one or more unique location IDs that serve to identify ageographic address or location of the frame arm 116 in which the workerPROM image 140 is stored, e.g., to identify a geographic address orlocation of a corresponding FRU 112. For instance, the location record304 may include a “physical” location ID 308 that identifies a locationwithin the frame 100 of a FRU 112 that is directly or physicallyinterconnected to the connector 128 of a corresponding frame arm 116(e.g., a FRU 112 connected to frame arm 116 #2 could have acorresponding physical location ID 308 of “2” while a FRU 112 connectedto frame arm 116 #6 could have a corresponding physical location ID 308of “6”). In one arrangement, the physical location ID 308 may provide aparticular offset U (e.g., offset rack unit number) within the frame100.

The location record 304 may also include one or more “non-physical”location IDs 312, each of which identifies a location of at least oneFRU 112 that is indirectly interconnected to a corresponding frame arm116 via another FRU 112 that is directly interconnected to the frame arm116. For instance, FIG. 10 illustrates another embodiment of the frame100′ in which the connector 132 of a FRU 112′ that is in the form of ablade enclosure is interfaced with the connector 128 of a correspondingframe arm 116. The FRU 112′ includes a plurality FRUs 112″ in the formof blade servers appropriately mounted within the FRU 112′. In thiscase, the location record 304 of the corresponding worker PROM image 140of the frame arm 116 may include a physical location ID 308 thatidentifies a location of the FRU 112′ within the frame 100′ as well as aplurality of non-physical IDs 312 that identify locations within theframe 100′ of the plurality of FRUs 112″. For instance, a chassismanagement module (CMM) (not shown) of an Oracle Sun Netra 6000 chassis(e.g., FRU 112′) connected to a frame arm 116 #8 may be identified by aphysical location ID 308 of “8” and the OOB service processor 164 of ablade server (e.g., FRU 112″) disposed within a “slot #3” of the chassismay be identified by a non-physical location ID 312 of “131” (0x83).

When the location record 304 of a particular worker PROM image 140includes one or more non-physical location IDs 312, the location record304 may also include a subordinate location ID list 316 that maps orotherwise links the non-physical location IDs 312 (i.e., IDs thatidentify the FRUs 112″ relative to the frame 100) to local devicenumbers 320 (i.e., IDs that identify the FRUs 112″ relative to the FRU112′) and which may be used by the FRU 112′ to configure the FRUs 112″in a manner free of having to wait for communication with the serviceprocessor 160 and/or frame manager 168. The location record 304 may alsoinclude an “identification” byte 332 that identifies a role of the FRU112 within the frame (e.g., role as the frame manager 168, role as aworker FRU, and the like). For instance, the identification byte 332 ofthe worker PROM image 140 of the frame center 120 may be set to a “framemanager” role so that upon installation of the frame center 120 into theframe 100, the frame center 120 proceeds to function as the framemanager 168.

The subnet IP record 316 includes a base management subnet IP address328 that broadly provides the OOB service processor 164 of each FRU 112with the information it needs to communicate with the frame center 120,service processor 160 and/or frame manager 168, and/or other FRUs 112.More specifically, individual addresses (e.g., of other FRUs 112) may bederived by using the subnet IP address 328 as the network address andthe physical or non-physical location ID 308, 312 as the host address.

Referring back to FIGS. 1 and 7, the attempting to read step 208 of themethod 200 may include an OOB service processor 164 of the first FRU 152attempting to read the physical and/or non-physical location IDs 308,312 of the location record 304 of the worker PROM image 140. Thereafter,the method 200 may determine 212 whether the location record 304 can beread. Responsive to a negative determination at 212, the method 200 mayproceed to 216 where the first FRU 152 may be operated in a “normal”mode (e.g., a mode of operation that is free of association with themanagement service context of the frame 100). Responsive to a positivedetermination at 212, the method 200 may proceed to 220 at which pointthe first FRU 152 may be operated in a “smart frame” mode (e.g., a modeof operation that is at least partially controlled or dictated by themanagement service context of the frame 100). Part of the result of apositive determination at 212 may be the frame manager 168 instructingthe main processor(s) on the first FRU 152 to power up.

As shown in FIG. 7, the operation 220 of the first FRU 152 in smartframe mode may include determining 224 a role of the first FRU 152within the frame 100, such as via the OOB service processor 164 readingand interpreting a bit mask of the identification byte 332 of the workerPROM image 140. For instance, responsive to a positive determination toa query 228 as to whether the role is a worker FRU, the method 200 mayproceed to 232 where the first FRU 152 may be operated 232 in a mannerthat is generally subservient to the frame manager 168 (e.g., in amanner in which the first FRU 152 is managed by the frame manager 168).Responsive to a negative determination to the query 228, the method 200may proceed to query 236 whether the determined role is a frame manager.

More specifically, while the frame manager 168 has generally beendescribed and illustrated as being implemented by the frame center 120,this is not always necessarily the case. For instance, the bit mask ofthe identification the first FRUs 152 byte 332 of worker PROM image mayindicate the role of the frame manager. Upon determining such a role,the method 200 may proceed to obtain 244 management records from amanager PROM image 148 of the first frame arm 156 and then manage 248worker FRUs (and possible additional FRUs) of the frame 100 according tothe obtained management records (e.g., via a frame manager 168 runningon the first FRU 152 in conjunction with the service processor 160 ofthe frame center 120).

For instance, upon initial configuration of the frame 100 and/or at anyother appropriate time, an administrator or other user may load orotherwise store the manager PROM image into the memory 136 of a selectedframe arm 116 (in addition to setting the bit mask of the identificationbyte 332 of the worker PROM image 140 of the selected frame arm 116 tocorrespond to a frame manager role). In one arrangement, each FRU 112may store a copy of the frame manager 168 in the memory 158 that it mayrun upon determining that it has a frame manager role. In anotherarrangement, a FRU 112 may, upon determining that it has a frame managerrole, obtain a copy of the frame manager 168 from any appropriatelocation (e.g., another FRU 112, the frame center 120, higher levelcomponents, and the like) via communication channels 124 for storage inmemory 158 and subsequent execution. FRUs may also operate 240 accordingto other various types of roles which are encompassed within the scopeof the present disclosure.

In any case, the service processor 160 and/or frame manager 168 utilizethe manager PROM image 148 information as part of managing the FRUs 112of the frame 100. Turning now to FIG. 9, the manager PROM image 148includes the location records 304 of all of the worker PROM images 140associated with installed FRUs 112 and the frame center 120 as well asthe subnet IP record 324. In this regard, the service processor 160and/or frame manager 168 can derive individual addresses of each of theinstalled FRUs 112 and the frame center 120 using the location records304 and subnet IP record 316 for use in communications between the same.The manager PROM image 148 may also include a configuration data record340, power and cooling requirement records 348, frame arm addressrecords 352, and/or the like.

The configuration data record 340 generally stores configurationinformation specific to FRUs 112 installed at particular frame arms 116in the frame 100. As shown, the configuration data record 340 may storethe configuration information by way of a plurality of “policy” bytes344 that are tagged with specific location records 304 (e.g., withspecific physical location IDs 308). For instance, the configurationdata record 340 may include a “hot-swap” policy byte 344 having aparticular bit mask for each of the location IDs 308 indicating whetherhot-swapping of a FRU 112 associated with the location ID 308 isdisabled, activated, deactivated, and the like. As another example, theconfiguration data record 340 may include a “firmware” policy byte 344specifying whether a FRU's 112 firmware, upon joining the framemanager's 168 configuration, is to be checked to determine whether thefirmware is of a particular version, must be automatically upgraded,does not need to be checked, and the like. Numerous other types ofpolicy bytes 344 are envisioned such as a “memory size” byte 344 (e.g.,specifying minimum required available memory in an installed FRU 112 ofa particular frame arm 116 as identified by physical location ID 308),an “installed type” byte 344 (e.g., specifying one or more particulartypes of FRUs that can be installed at a particular frame arm 116 asidentified by physical location ID 308), a “network connections” byte344 (e.g., specifying one or more particular types of networkconnections that an installed FRU 112 needs to have), and the like.

The configuration data record 340 (as with the other records disclosedherein) may be arranged and organized in any appropriate manner. Forinstance, the configuration data record 340 may be arranged in a tableor database format whereby physical and/or non-physical location IDs308, 312 may populate a first row or first column, each of the variouspolicy bytes 344 may populate the other of the first row or firstcolumn, and bit masks of the various policy bytes 344 may populate cellsin the table for each of the location IDs. The service processor 160and/or frame manager 168 may access the configuration data record 340 aspart of managing FRUs 112 installed in the frame 100. In onearrangement, the makeup of the manager PROM image 148 may reflect FRUs112 currently installed in the frame 100. More specifically, in theevent that a frame arm 116 is free of a FRU 112 being directlyinterfaced therewith, the manager PROM image 148 may also be free ofinformation (e.g., location records 308, policy bytes 344, and the like)specific to the worker PROM image 140 of the frame arm 116 and FRUs 112to be installed at the frame arm 116. Also, in the event that a FRU 112is installed in a particular frame arm 116 and joins the frame'smanagement service context or network, the service processor 160 and/orframe manager 168 may facilitate the updating of the manager PROM image148 to reflect information specific to the frame arm 116 and FRUs 112installed at the frame arm 116. In another arrangement, the manager PROMimage 148 may store information specific to a frame arm 116, policybytes 344, and the like whether or not a FRU 112 is installed on theframe arm 116.

In relation to different frame configurations, the information stored inthe manager PROM image 148 may change (e.g., to account for a new ordifferent configuration) while the information in the worker PROM images140 may remain largely static. For instance, imagine a firstconfiguration in which half of the frame arms 116 of a frame 100 arepopulated with FRUs 112, where each of the populated frame arms 116includes a respective worker PROM image 140. Further imagine a secondconfiguration of the frame 100 in which one or more of the previouslynon-populated frame arms 116 of the frame 100 are now populated with oneor more FRUs 112. Here, while the manager PROM image (e.g., stored inthe frame center 120 and/or one of the FRUs 112) may be updated toaccount for the newly added FRUs 112, each of the worker PROM images 140corresponding to installed FRUs 112 that are common between the firstand second configurations may remain the same. However, it should beunderstood that when a particular FRU 112 installed in a frame arm 116is replaced with a different FRU, the information of the worker PROMimage 140 (and thus the manager PROM image 148) in the frame arm 116 mayin some situations correspondingly change. For instance, in the eventthat a 2U FRU 112 installed at one or two frame arms 116 is replacedwith a 4U FRU 112 installed at the same one or two frame arms 116, thelocation record 304 of the worker PROM image(s) 140 of the frame arm(s)116 may be appropriately updated to reflect a different “rack locationheight” (e.g., due to the difference in height between a 2U FRU and a 4UFRU).

As an example of how the service processor 160 and/or frame manager 168manage installed FRUs 112, imagine the first FRU 152 runs the framemanager 168 and that a second FRU 172 (see FIG. 1) is interfaced with asecond frame arm 176 of the frame 100. Further assume that the OOBservice processor 164 of the second FRU 172 can read the location record304 of the worker PROM image 140 stored in the second frame arm 176 anddetermines (e.g., upon reading the identification byte 332) that it is aworker FRU. Upon determining by the frame manager 168 that a worker FRU(i.e., the second FRU 172) has been installed in the frame (e.g., byreceiving an alert from the service processor 160 via a respectivenetwork line 24 that the service processor 160 has received an interruptsignal from the second FRU 172 via a respective I²C line 20 indicatinginsertion of the second FRU 172), the frame manager 168 may access themanager PROM image 148 of the first frame arm 156 and obtain managementrecords tagged with the physical location ID 308 of the second frame arm176 for use in managing the second FRU 172.

For instance, upon the frame manager 168 receiving a request from theOOB service processor 164 of the second FRU 172 to join its network(i.e., the frame's 100 network), the frame manager 168 may query the OOBservice processor 164 of the second FRU 172 for various specificationsor properties of the second FRU 172, such as current firmware version,available memory, network connections, motherboard revision, producttype, PCI root and leaf node configuration, and/or the like. Uponreceiving the specifications, the frame manager 168 may analyze orevaluate the received specifications in relation to the particularpolicy byte bit masks associated with the second frame arm 176 physicallocation ID 308 and take one or more actions based on a result of theevaluation. As an example, upon the frame manager 168 determining thatthe second FRU 172 needs to update its current firmware to a newerversion, the frame manager 168 may disallow the joining of the secondFRU 172 to the frame's network until the second FRU 172 updates itsfirmware. As another example, upon receiving a request from the OOBservice processor 164 of the second FRU 172 to bring one or moreapplications online (e.g., available for use by other FRUs 112 and/orhigher level components or processes), the frame manager 168 may querythe OOB service processor 164 for the current network connections of thesecond FRU 172 (e.g., which switches the second FRU 172 is connectedto), and allow or disallow the bringing of the application(s) onlinebased on a result of the network connection query by the frame manager168.

In one arrangement, a user may, upon desiring to hot-swap the second FRU172, depress or manipulate a button or other feature (e.g., button 182in FIG. 4) on the back of the second frame arm 176 to cause thetransmission of a hot-swap request to the service processor 160 of theframe center 120 via a respective I²C line 20 of the fixed interconnecttopology 124 electrically connecting the second frame arm 176 to theframe center 120. Upon receipt of the request, the service processor 160may forward the request to (or otherwise alert) the frame manager 168 atthe first FRU 152 via a respective network line 24 between the framecenter 120 and the first frame arm 156 to perform a hot-swap operationof the second FRU 172. In response, the frame manager 168 accesses andevaluates the “hot-swapping” policy byte 344 in the configuration datarecord 340 of the manager PROM image 148 that is tagged with thephysical location ID 308 associated with the second frame arm 176 todetermine whether or not hot-swapping of the second FRU 172 is allowed,and then correspondingly allows or disallows hot-swapping based on aresult of the evaluating. For instance, an LED 180 on the second framearm 176 may assume respective first and second conditions (e.g.,blinking or not blinking) responsive to the frame manager 168determining that hot-swapping of the second FRU 172 is either allowed ornot allowed.

As discussed previously, the frame center 120 is interconnected to eachof the frame arms 116 by way of the fixed interconnect topology 124 andgenerally facilitates the routing of communications among installed FRUs112. In this regard, the frame center 120 (e.g., the service processor160) accesses the frame arm address record 352 of the manager PROM image148 to determine how to route a particular communication to a particularframe arm 116 (and thus a FRU 112 installed at the particular frame arm116). In one arrangement, the frame arm address record 352 may mapphysical hardware addresses and port numbers to physical location IDs308. For instance, upon a FRU 112 seeking to bring one or moreapplications online, the OOB service processor 164 of the FRU 112 maygenerate a request that includes a destination physical or non-physicallocation ID 308, 312 associated with the frame manager's FRU 112 andpass the request to the frame center 120 (e.g. over the respectivenetwork line 24 electrically interconnecting the frame center 120 to theframe arm 116 with which the FRU 112 is interfaced). Upon receipt of therequest at the frame center 120, the service processor 160 may utilizethe destination physical or non-physical location ID 308, 312 to obtaincorresponding physical hardware address(es) and port number(s) (e.g., ahardware path) and then route the request to such obtained physicalhardware address(es) and port number(s) over the particular network line24 electrically connecting the frame center 120 to the frame arm 116associated with the obtained physical hardware address(es) and portnumber(s). In one arrangement, the service processor 160 propagateschanges to the subnet IP record 316 to the frame arms 116 for updatingof the respective worker PROM images 140.

FIGS. 10-11 illustrate other embodiments of the frame 100. As discussedpreviously, FIG. 10 illustrates an embodiment in which the connector 132of a FRU 112′ in the form of a blade enclosure or chassis is interfacedwith the connector 128 of a corresponding frame arm 116, and the FRU112′ includes a plurality FRUs 112″ in the form of blade serversappropriately mounted within the FRU 112′. FIG. 11 illustrates a smartframe system 396 in which first and second 397, 398 frames (e.g., frames100) respectively installed within first and second racks 104 may beinterconnected by any appropriate communication channel(s) orinterconnect 399 (e.g., cable, harness) for use in increasing processingand memory capacity and/or the like. In this arrangement, a single framemanager 168 implemented at the frame center 120 or a FRU 112 of eitherthe first or second frame 397, 398 may manage all FRUs 112 installed onthe first and second frames 397, 398. That is, one of the first andsecond frames 397, 398 may be free of a frame manager 168. For instance,communications between a frame manager 168 residing on the first frame397 and a FRU 112 on the second frame 398 may be passed to the framecenter 120 of the second frame 398 which proceeds to analyze thecommunication (in conjunction with the manager PROM image 148) todetermine which FRU 112 the communication is to be routed to.

In one arrangement, the manager PROM image 148 may conform to IPMIPlatform Management FRU Information Storage Definition version 1.0.Provided below is one example of a management record specification foruse with the frame 100 disclosed herein with the understanding that thepresent disclosure is not limited to the specific format presentedbelow. Rather, it is only provided as an example to present the readerwith one manner in which the present disclosure can be implemented.

Primary Records

Location Record:

Location ID Field Type Size Value Sub Record ID Data 1 0x02 Record DataField Type Size Location ID Data 2 Identification Byte Data 1 RackLocation Bottom Data 1 Rack Location Height Data 1 Frame managerLocation ID 1 Data 1 Frame Manager Location ID 2 Data 1 Start ofSubordinate Location ID List Struct Variable

There may exist four types of “Location IDs” in the location record:

Location ID Range Location ID Type 0x00.00 Null Location ID 0x00.01 to0x00.FD Physical Location IDs 0x01.00 to 0x0F.FF Non Physical LocationIDs 0x00.FE Virtual Fame Manager ID

Each location ID may be two bytes in length and have the following bitdefinitions:

Bits 12-16 Bits 8-11 Bits 4-7 Bits 0-3 Frame ID Non-Physical Location ID

The “Rack Location” fields may be populated for corresponding PhysicalLocation IDs. The Frame ID may be utilized in multi rack configurations.The “Identification Byte” of the location record may be used todetermine role information, and may be used by the frame center duringthe programming process. The Identification Byte may contain a bit maskwith the following definitions:

Identification Byte Bit Mask 0x00 Empty (No Attachment) 0x01 FrameManager Bit 0x02 Worker Bit 0x04 Blade Server Bit 0x08 Frame Center Bit0xF0 Reserved Bits

The Frame Manager Bit may not be mutually exclusive. For example, aworker FRU that has Frame Manager functionality in one logical domain(LDOM) and worker functionality in another LDOM may have anIdentification Byte value of 0x03 whereas a worker FRU free of FrameManager functionality may have a value of 0x02.

The Subordinate Location ID List may contain a series of devicenumber-to-Location ID mappings. The list may terminate with a LocationID of zero. This information can be used by an entity FRU (e.g.,enclosure or chassis) with subordinate attachment FRUs (e.g., bladeservers) so that it can configure its attachments free of having to waitfor Frame Manager communication. Software may ensure that these mappingsare consistent with a corresponding FRU Configuration Data Record (shownbelow). If the Frame Manager Location ID is non-zero within the LocationRecord, then it holds a Location ID of a non-physical Frame Manager(e.g., one not connected directly to a Frame Arm such as a blade withina blade server). If there is no corresponding Frame Manger within thisattachment, then the entry has a value of zero.

Subordinate Location ID List Field Type Size Non Physical Location IDData 2 Device Number Data 1

Subnet IP Record:

The base management Subnet IP address may be stored in the worker PROMimage of each frame arm to provide each FRU's OOB service processor theinformation it needs to communicate with the Frame Manager. Individualmanagement addresses may be derived by using the Base Management SubnetIP as the network address and the Location ID as the host address. FrameCenter software may ensure that a change to this address is propagatedto each Frame Arm location as well as the Frame Center Image.

Base Management Subnet IP Record Field Type Size Value Sub Record IDData 1 0x03 Record Data Field Type Size Base Subnet IP Data 4 Net MaskData 4

Configuration Data Record:

The Configuration Data Record may hold most of the information specificto each Location ID. The Frame Manager may access this data and compareit to the installed FRU. FRU components that are intended to be checkedmay implement a policy byte that the Frame Manager evaluates todetermine what action to take if the component fails to meet a minimumrequirement (e.g., not enough memory installed).

FRU Configuration Data Record Field Type Size Value Sub Record ID Data 10x04 Record Data Field Type Size Location ID Data 2 Parent Location IDData 2 Device Number Data 1 Number of I/O port records Data 1 Hot SwapPolicy Data 1

Frame Arm Address Record:

The Frame Arm Address Record maps physical hardware addresses and portnumbers to Frame Arm Identifier (e.g., Location IDs). It may bereferenced by the Frame Center. This record may include a list ofstructures that terminating with a Frame Arm identifier of zero.

Frame Arm Hardware Address Map Field Type Size Value Sub Record ID Data1 0x07 Record Data Field Type Size Frame ID Data 1 Start of Address MapList Structure Variable

The Address Map List may include a series of Location IDs to hardwareaddress map associations. The list may terminate with a Location ID ofzero.

Address Map List Structure Field Type Size Frame Arm ID (PhysicalLocation ID) Data 2 I2C Expander Address Data 1 I2C Expander Port NumberData 1

Optional Records

FRU I/O Port Definition Record:

The FRU I/O Port Definition Record describes each I/O port for a givenLocation Record. These descriptions may be used in Point to PointConnection Records (discussed below) and may span multiple records toaccount for FRUs with many ports. The FRU I/O Port Definition Recordwill have the following specifics:

FRU I/O Port Definition Record Field Type Size Value Sub Record ID Data1 0x05 Record Data Field Type Size Location ID Data 2 I/O Port RecordNumber Data 1 Start of I/O Port List Structure Variable

The I/O Port List may contain a series of port ID to port typeassociations. Port IDs may be unique to a given Location ID. The portlist for the specific record number may terminate with a port ID ofzero.

I/O Port List Field Type Size Port ID Data 2 I/O Port Type Data 1 I/OPort Number Data 2

Point to Point Connection Record:

The Point to Point Connection Record defines all I/O port interconnectswithin a frame. Each connection entry may contain a policy byte that theFrame Manager may use to determine whether a connection should beverified and what action to take if the connection verification fails.

Point to Point Connection Record Field Type Size Value Sub Record IDData 1 0x06 Record Data Field Type Size Connection Record Number Data 1Start of Connection List Structure Variable

The Connection List may contain a series of connection records withpoint to point associations. For a given record, the Connection List mayterminate with a Connection ID of 0. Software may ensure that all Pointto Point connection records are evaluated.

Connection List Structure Field Type Size Connection ID Data 2 LocationID A Data 2 Port ID A Data 2 Location ID B Data 2 Port ID B Data 2Policy Byte Data 1

Dynamic Management Data

Dynamic Management Data may be used by the management framework, and maybe considered dynamic in that it may change more frequently than theconfiguration. The Dynamic Management Data may be held in Frame Managerconfiguration files rather than PROM images.

Dynamic FRU Configuration Data Field Type Size Location ID Data 1 TypeIdentifier Date 1 Type Policy Data 1 Product Description String OffsetString variable Memory Requirement (in MB) Data 4 Memory Check PolicyData 1 Firmware Requirement List Offset String List 1 Firmware ComponentString variable Policy Byte Data 1

Policy Byte Definitions

Bit Installed Memory PtoP Hot Mask Type Size Firmware Connection Swap0x00 No Check No Check No Check No Check Disabled 0x01 Type MinimumMinimum Check Activation 0x02 Architecture Reserved Reserved ReservedDeactivation 0x04 Model Reserved Reserved Reserved Reserved 0x08Reserved Exact Exact Reserved Reserved 0x10 Warn Warn Warn Warn Warn0x20 Disable Disable Disable Disable Reserved App App App App 0x40Reserved Reserved Auto Reserved Reserved Upgrade 0x80 No No No NoReserved Activation Activation Activation Activation

Type Identifier and Port Type List

Value FRU Type 0x00 NULL Type 0x10 RMS 0x11 RMS: SPARC 0x12 RMS: x860x20 Switch 0x21 Switch: Fast Ethernet 0x22 Switch: Gigabit Ethernet0x23 Switch: 10 Gigabit Ethernet 0x24 Switch: 40 Gigabit Ethernet 0x28Switch: Infiniband 0x30 Storage 0x31 Storage: SCSI 0x32 Storage: SAS0x40 Blade Server 0x41 Blade: SPARC 0x42 Blade: X86 0x62 USB 0xC0 PDU

Turning now to FIG. 12, a rear portion of one representative example ofa smart computing frame 400 (e.g., frame 100 of FIG. 1) is illustratedthat may be used to efficiently manage a wide variety of FRUs such asrack-mount servers, backup power modules, and/or the like of one or moreform factors such as 1U, 2U, and/or the like. As shown, the frame 400may be installed or otherwise disposed within a rack or cabinet 404including width, height and depth dimensions 405, 407, 409 and may begenerally made up a plurality of vertical support members or rails 408that are interconnected by a plurality of horizontal support members 411to form a framework. The rack 404 may include a plurality of pairs ofrail assemblies 401 disposed along the height dimension 407 (or otherdimension) of the rack 404, where each rail assembly 401 extends alongthe depth dimension 409 of the rack between opposing vertical members408. Each pair of rail assemblies 401 may define one of a plurality ofreceiving bays 410 for receiving one of a plurality of FRUs 412.

Adjacent a rear portion of each of the receiving bays 410, the frame 400may include a respective frame arm 416 (e.g., frame arm 116) thatfacilitates electrical interconnection of a respective FRU 412 to aframe center (not shown, e.g., frame center 120) and one or more PDUs(not shown, e.g., PDUs 508, 512) through a fixed interconnect topology424 (e.g., fixed interconnect topology 124). Turning now to FIG. 13, aclose-up perspective view of one of the frame arms 416 is presented,where the frame arm 416 may be secured to an outer rail member 450 ofone of the pair of rail assemblies 401 of a receiving bay 410 adjacent arear portion of the receiving bay 410 in any appropriate manner. In thisregard, a FRU 412 (not shown in FIG. 13) being installed into thereceiving bay 410 via the outer rail member 450 may be automaticallyaligned with the frame arm 416 so that continued insertion of the FRU412 may eventually result in interfacing and electrically connectionbetween the FRU 412 and the frame arm 416 as will be discussed below.

The frame arm 416 generally includes a housing 418 (e.g., housing 118)non-movably securable in any appropriate manner relative to the outerrail member 450 of one of the pair of rail assemblies 401 of theparticular receiving bay 410. In one arrangement, the housing 418 mayinclude a pair of grooves 419 adjacent a side portion thereof that areconfigured to receive a corresponding pair of flanges 421 of the outerrail member 450. In this regard, the housing 418 can be slid along theouter rail member 450 to a desired location (e.g., adjacent a rearportion of the receiving bay 410) and then non-movably secured to theouter rail member 450 in any appropriate manner (e.g., via tightening abolt (not shown) extending through the housing 418 against the outerrail member 450). Other manners of securing the housing 418 to the rack404 adjacent a rear portion of the receiving bay 410 are also envisionedand encompassed within the scope of the present disclosure.

The frame arm 416 may also include a PCB 422 (e.g., PCB 122) secured toa portion (e.g., side) of the housing 418 (e.g., via passing fasteners417 through apertures (not shown) in the PCB 422 and into apertures (notshown) in the housing 418) having a memory storing location data of theframe arm 416 within the frame 400, serial to I²C conversion logic,LEDs, and the like (not labeled, but similar to the PCB 122 in FIG. 4).Furthermore, a connector 428 (e.g., connector 128, such as a blind-mateconnector) is electrically connected and secured in any appropriatemanner to the PCB 422 to facilitate electrical connection between arespective FRU 412, the frame center, and one or more PDUs via the fixedinterconnect topology 424. More specifically, at least one I²C cable orline (e.g., I²C line 20, not shown in FIG. 13) may be electricallyconnected between the frame center and the PCB 422 (e.g. to an I²C databus via a bottom portion of the PCB 422 facing the outer rail member450, not visible in FIG. 13), at least one network cable or line (e.g.,network line 24, not labeled in FIG. 13) may be electrically connectedbetween the frame center and pins/contacts (not shown) adjacent a rearportion 470 of the connector 428 (and thus may “pass-through” the PCB422), and at least one power line or cable (e.g., power lines 28, 32)may be electrically connected between one or more PDUs (e.g., PDUs 508,512) and pins/contacts adjacent the rear portion 470 of the connector428.

To facilitate precise alignment between the connector 428 of the framearm 416 and the corresponding connector 432 of a FRU 412 (not shown inFIG. 13, but discussed below in relation to FIGS. 14-19), the frame arm416 may include at least one mechanical connector or alignment componentin the form of an alignment pin 429 that is configured to be received ina corresponding mechanical connector or alignment component in the formof a alignment barrel 740 of an adapter 700 (e.g., “frame backplaneadapter”) of the FRU 416 (discussed below). The alignment pin 429 may besecured to a portion of the housing 418 so as to face the same directionas does the connector 428 (i.e., towards an oncoming FRU 416 beinginserted into the receiving bay 410) but be at least slightly spacedfrom the connector 428. For instance, the alignment pin 429 may includea lock or stop nut 430 in addition to a threaded end (not shown) thatmay be inserted through at least one aperture 431 in a wall of thehousing 418. A threaded nut (not shown) may be threaded over thethreaded end of the alignment pin 429 on an opposing side of the wall ofthe housing 418 so that the nut 430 abuts or contacts the housing wallto rigidly secure the alignment pin 429 to the frame arm 416. In oneembodiment, the threaded nut may be removed from the threaded end andthe threaded end may be inserted into a different one of the apertures431 in the wall of the housing 418 to effect a desired height of thealignment pin 429.

As shown, the alignment pin 429 may include a tip portion 437 (e.g.,which may be tapered) to facilitate initial location of the alignmentpin 429 in the alignment barrel 740 of the adapter 700 of the FRU 412.The alignment pin 429 may also include an enlarged head portion 435 thatis adapted to interact with a peripheral edge of the alignment barrel740 to at least partially lock or secure the alignment pin 429 againstmovement relative to the alignment barrel 740 upon interfacing of theconnectors 428, 432 of the frame arm 416 and the FRU 412. Anyappropriate cover, shield or the like (not shown) may be secured to thehousing 418 over the PCB 422 (e.g., via fasteners 417) to protect thevarious components of the PCB 422 from damage. In one arrangement, oneor more support arms or brackets (not shown) may rigidly interconnectthe housing 418 of the frame arm 416 to an opposing outer rail member450 of an opposing rail assembly 401 of the same receiving bay 410 tofurther support the frame arm 416 and provide for a more robust frame400 and/or rack 404.

With reference now to FIGS. 14-15, presented are perspective views of anadapter 700 (e.g., a connector arrangement) that is configured to allowa FRU 412 to be inserted into a receiving bay of a computing rack andsubstantially seamlessly electronically discovered by managementservices software of the computing rack by way of blind mate interfacingbetween the adapter 700 and the receiving bay (e.g., a frame arm 416 ofreceiving bay 410) of the computing rack. For instance, the adapter 700may at least partially represent the arrangement 134 of brackets,linkages, and/or the like discussed in relation to FIG. 4 that isadapted to non-movably secure the connector 132 to the FRU 112 so thatthe connector 132 can electrically interface with the connector 128 ofthe frame arm 116 during insertion of the FRU 112 into a receiving bayof the computing rack 104. The adapter 700 may be added to an existing,standard, rack-mount FRUs to quickly adapt the FRU for use in blind-mateinstallations (such as in the frame 400 of FIG. 12) or may be built intoa FRU as part of initial construction of the FRU to allow the FRU to beused in such blind-mate installations.

Broadly, the adapter 700 includes a mounting portion 704 (e.g., one ormore brackets) that is configured to be non-movably secured to a FRU 412and an attachment portion 708 (e.g., one or more brackets) extendingfrom the mounting portion 704 that is configured to receive a connector432 (e.g., blind mate connector 132 of FIG. 4) to allow the connector toelectrically interface with a corresponding connector 428 (e.g.,connector 128) adjacent a rear of a receiving bay 410 of a computingrack as the FRU 412 is being inserted into the receiving bay 410. In onearrangement, the mounting portion 704 may include a first mountingmember 712 (e.g., plate, flange, etc.) that is configured to benon-movably secured relative to the FRU 412. For instance, the firstmounting member 712 may be rigidly secured (e.g., via fasteners, nuts,and aligned holes, not labeled) to an inside portion of an inner railmember 454 of the same rail assembly 401 to which one of the frame arms416 of the frame 400 is secured (e.g., where the frame arm 416 issecured to the outer rail member 450 of the rail assembly 401 and thefirst mounting member 712 is secured to the inner rail member 454 of thesame rail assembly 401).

In this regard, rigid mounting of the inner rail member 454 to a sideportion 413 of the FRU 412 (e.g., via threading fasteners (not shown)through attachment components such as apertures 458 in the inner railmember 454 and corresponding apertures (not shown) in the side portion413 of the FRU 412) serves to non-movably or rigidly secure the adapter700 to the FRU 412. In another arrangement, the mounting portion 704 mayadditionally or alternatively include a second mounting member 716(e.g., plate, flange, etc.) that is spaced from the inner rail member454 and that is configured to be non-movably secured to the side portion413 of the FRU 412 (e.g., via threading fasteners (not shown) throughapertures 720 in the second mounting member 716 and correspondingapertures (not shown) in the side portion 413 of the FRU 412).

With reference now to FIGS. 14-18, the attachment portion 708 mayinclude an attachment member 728 (e.g., plate, bracket, flange, etc.)extending from the mounting portion 704 and having a receiving aperture732 (labeled in FIGS. 14 and 17) extending therethrough that is sizedand configured to fixably receive the connector 432 therein so as toface a front portion 438 of the connector 432 towards a front portion472 of the connector 428 of a corresponding frame arm 416 duringinsertion of the FRU 412 into the receiving bay 410. For instance, theconnector 432 may include one or more flexible tangs, clips or the like(not shown) that are adapted to snap past an inner wall of the receivingaperture 732 and thereby lock or non-movably fix the connector 432 tothe attachment portion 708 and thus to the FRU 412 (i.e., when themounting portion 704 is non-movably fixed to or at least relative to theFRU 412). However, other manners of securing the connector 432 to theattachment portion 708 are also envisioned and encompassed herein.

In any event, it can be seen how the mounting portion 704 and the innerrail member 454 space the attachment portion 708 of the adapter 700 adistance 724 (labeled in FIGS. 16 and 18) from a rear portion 414 of theFRU 412 to advantageously provide room for one or more cables, wires,and/or the like that electrically connect power, serial, and networkports adjacent the rear portion 414 of the FRU 412 to the connector 432secured to the attachment portion 708 of the adapter 700. For instance,FIGS. 16-18 illustrate how a plurality of cables 736 (e.g., network line40; power lines 52, 56; serial data line 64 of FIG. 4) may respectivelyelectrically connect various ports 737 (e.g., network port 36; powerports 44, 48; serial management port 60 of FIG. 4) of the FRU 412 toappropriate pins/contacts (not shown) adjacent a rear portion 433 of theconnector 432. As shown, the first and second mounting members 712, 716and attachment member 728 may collectively form at least a partialhousing for containing the plurality of cables 736. In any case,electrical interfacing of respective pins/contacts adjacent the frontportions 434, 472 of the connectors 432, 428 (e.g., during insertion ofthe FRU 412 into the receiving bay 410 of the rack 404 as discussedbelow) automatically allows the FRU 412 to draw power from one or morePDUs 126; network communications to occur between the frame manager (notshown; e.g., frame manager 168 of FIG. 1), service processor of theframe center (not shown, e.g., service processor 160 of FIG. 5) and theOOB service processor (not shown; e.g., ILOM 164 shown in FIG. 1) of theFRU 412; and requests from the OOB service processor of the FRU 412 toread information (e.g., such as location data 141, role information,etc.) from the memory (not labeled) of the PCB 422 to be fulfilled.

As discussed previously, the frame arm 412 may include at least onemechanical alignment component in the form of an alignment pin 429 thatis configured to be received in a corresponding mechanical alignmentcomponent in the form of a alignment barrel 740 of the adapter 700 tofacilitate precise and secure alignment and electrical interfacingbetween the connector 428 of the frame arm 416 and the connector 432 ofthe FRU 412. With respect to FIGS. 14, 16 and 17, the alignment barrel740 may be disposed in or on the attachment portion 708 of the adapter700 adjacent or spacedly adjacent the connector 432. As shown, thealignment barrel 740 may include opposed front and rear portions 744,748 and a receiving opening or bore 752 extending through the alignmentbarrel 740 between the front and rear portions 744, 748. While thealignment pin 429 and alignment barrel 740 have been discussed as beingrespectively disposed on the frame arm 416 and adapter 700, otherarrangements envision that the alignment pin 429 and alignment barrel740 could instead be disposed on the adapter 700 and frame arm 416,respectively.

To facilitate the reader's understanding of how a FRU (e.g., FRU 412)may be inserted into a computing rack (e.g., rack 404) and allowed tosubstantially seamlessly (e.g., blind-matingly) join the managementnetwork of the rack, reference will now be made to FIG. 20 whichillustrates one method 800 of inserting a FRU into a computing rack soas to electrically interface the FRU with a frame center of the rack. Itis to be understood, however, that other methods including more, fewer,or alternative steps are also envisioned and encompassed herein.Additionally, while the method 800 will be discussed in the context ofFRU 412 being inserted into a receiving bay 410 of rack 404 andelectrically and mechanically interfacing with a frame arm 416 of thereceiving bay 410, it is to be understood that the method 800 may bepracticed in conjunction with other FRUs, computing racks, etc. thanthose specifically illustrated herein.

At 804, ends 462 (e.g., see FIG. 16) of a pair of inner rail members 454of FRU 412 may be respectively inserted into channels 451 of a pair ofouter rail members 450 of a receiving bay 410 of the computing rack 404(e.g., via a front portion of the receiving bay 410 that is opposed to aframe arm 416 disposed adjacent a rear portion of the receiving bay410). For instance, a first of the inner rail members 454 may be securedto both an adapter 700 and a first side portion 413 of the FRU 412 (asshown in FIGS. 14-17), and a second of the inner rail members 454 may besecured to an opposing second side portion (not shown) of the FRU 412.In one arrangement, the pair of inner rail members 454 may berespectively inserted into channels of a pair of intermediate railmembers 456 (see FIG. 18) that are respectively disposed within thechannels 451 of the pair of outer rail members 450 such that each set ofinner, intermediate and outer rail members 454, 456, 450 can slide orotherwise move relative to each other to facilitate insertion andremoval of the FRU 412 into and from the receiving bay 410. While theend 462 of one of the inner rail members 454 has been illustrated asextending past the end of the adapter 700 (e.g., past the end of themounting and attachment portions 704, 708, see FIGS. 15, 16 and 18),other arrangements encompassed herein envision that the end 462 extendsjust to or even short of the end of the adapter 700.

The method 800 may then include advancing 808 (e.g., sliding, moving,etc.) the FRU 412 towards the rear portion of the receiving bay 410(e.g., pushing on a front portion of the FRU 412 so that an opposed rearportion 414 of the FRU 412 moves towards a frame arm 416 adjacent a rearportion of the receiving bay 410). See FIG. 18 which illustrates a rearportion 414 of the FRU 412 during the advancing 808 of the FRU 412towards the frame arm 416 adjacent a rear of the receiving bay 410. Themethod 800 may then include mechanically aligning 812 the electricalconnector 432 of the FRU 412 with the corresponding electrical connector428 of the frame arm 416 (e.g., in preparation for precise electricalinterfacing 828 of the connectors 432, 428).

In one arrangement, the mechanical alignment 812 may initially includereceiving 816 the alignment pin 429 of the frame arm 416 through a frontportion 744 of the alignment barrel 740 of the FRU 412 (e.g., of theadapter 700 secured to the FRU 412), where the alignment pin 429 andalignment barrel 740 are spaced at least a substantially common distance(e.g., in the width dimension 405, see FIG. 12) from the frame armconnector 428 and FRU connector 432, respectively. With reference toFIGS. 13, 16 and 18, for instance, the tip portion 437 of the alignmentpin 429 may be configured to enter the receiving bore 752 of thealignment barrel 740 via the front portion 744 of the alignment barrel740 as the FRU 412 is advanced 808 within the receiving bay 410. Forexample, the alignment pin 429 and alignment barrel 740 may beconfigured and designed to be a substantially common distance from acommon reference line of the outer rail member 450 (or other referencelocation(s)) in each of the width and height dimensions 405, 407 (seeFIG. 12) so that the tip portion 437 is able to be substantially readilyreceived in the alignment barrel 740.

Thereafter, continued advancement 820 of the FRU 412 towards the rearportion of the receiving bay 410 may serve to more fully and preciselyalign the connectors 428, 432 (e.g., the corresponding pins/contacts ofthe connectors 428, 432) in both of the width and height dimensions 405,407. For instance, a camming action between the tapered tip portion 437and an outer peripheral edge of the receiving bore 752 adjacent thefront portion 744 of the alignment barrel 740 during the continuedadvancement 820 may tend to correct for any differences in tolerancesamong the various components of the rail assemblies 401, frame arms 416,FRUs 412, adapters 700, and/or the like to precisely align the alignmentpin 429 within the receiving bore 752 and thereby precisely align theconnections 428, 432 (e.g., due to the above-discussed commondistances). In one arrangement, an enlarged head portion 435 of thealignment pin 429 (labeled in FIG. 13) may have an outer diameter thatis substantially the same as an inner diameter of the receiving bore 752between the front and rear portions 744, 748 of the alignment barrel 740(e.g., so that there is a slight friction fit between the enlarged headportion 435 and the receiving bore 752 as the alignment barrel 740 ismoving relative to the alignment pin 429) to maintain theabove-discussed precise alignment initially achieved via engagementbetween the tip portion 437 and the outer peripheral edge of the frontportion 744 of the alignment barrel 740.

More specifically, configuring the outer diameter of the enlarged headportion 435 and the inner diameter of the receiving bore 752 to besubstantially the same limits relative movement between the alignmentpin 429 and the alignment barrel 740 (and thus between the connectors428, 432) in the width and height dimensions 405, 407 as the FRU 412 isadvancing (e.g., along the depth dimension 409) towards the rear portionof the receiving bay 410 into a fully mounted position. While only asingle set of an alignment pin 429 and alignment barrel 740 have beenshown in the figures, it will be readily appreciated that more than oneset of the same may be included to further facilitate precise alignmentof the connectors 428, 432. As just one example, two or more alignmentpins 429 may be received within respective apertures 431 in the wall ofthe housing 418 of the frame arm 416 while two or more respectivealignment barrels 740 may be included in the attachment member 728 ofthe adapter 700.

In one arrangement, the connectors 428, 432 may have one or morealignment posts 475 and alignment openings 476 (labeled in FIGS. 13 and16), where each alignment post 475 is configured to be received in arespective corresponding alignment opening 476 after at least onealignment pin 429 has been at least initially/partially received in acorresponding alignment barrel 740. In this regard, each alignment pin429/alignment barrel 740 combination may be considered a “primary”alignment mechanism (e.g., that serves to perform initial alignment ofthe pins/contacts of the corresponding connectors 428, 432) while eachalignment post 475/alignment opening 476 combination may be considered a“secondary” alignment mechanism (e.g., that serves to perform morefine-tuned alignment of the pins/contacts of the correspondingconnectors 428, 432). In any event, the method 800 may includeelectrically interfacing 828 the connectors 428, 432 after or uponmechanical alignment 812 of the connectors 428, 432. See FIG. 19. Atthis point, the FRU 412 may be substantially automatically and/orseamlessly discovered by the frame center (e.g., frame center 120 ofFIG. 1) and/or frame manager (e.g., frame manager 168 of FIG. 1) of thecomputing rack via the fixed interconnect topology 424, the frame centerand/or frame manager may conduct OOB management of the FRU 412, FRUhot-swap/removal requests may be generated by the frame arm 416 (e.g.,upon depression of a corresponding button on the frame arm 416) andpassed to the frame center for processing, and/or the like, all asdiscussed previously. One or more of the FRUs 412 of the rack 404 ofFIG. 12 may be inserted into and removed from respective receiving bays410 of the rack 404 so as to respectively join or disjoin the managementnetwork/context of the frame 400 in manners as discussed above using aplurality of substantially identical adapters 700, even in the casewhere the plurality of FRUs 412 collectively include different formfactors (e.g., 1U and 2U FRUs), different functions, and/or the like.

To assist in maintaining secure and consistent electrical contactbetween the pins/contacts of the connectors 428, 432 when the FRU 412 isfully mounted within the receiving bay 410, the enlarged head portion435 (e.g., a locking portion) of the alignment pin 429 may be configuredto interact and/or engage 824 with a locking portion in the form of alip or flange 753 adjacent the rear portion 748 of the alignment barrel740 to limit premature separation of the alignment pin 429 and thealignment barrel 740 (and thus of the connectors 428, 432). Morespecifically, the outer diameter of the enlarged head portion 435 may beat least slightly greater than an inner diameter of the flange 753 sothat the flange 753 would have to be at least slightly forced past theenlarged head portion 435 as the FRU 412 is being advanced into thefully mounted position. Stated differently, a user may have to exert aslightly greater force on the front of the FRU 412 to move the flange753 from a first side of the enlarged head portion 435 to an opposingside of the enlarged head portion 435. The connectors 428, 432 may beconfigured to be fully engaged/seated relative to each other once theflange 753 has been forced just past the enlarged head portion 435(e.g., just as the flange 753 has moved to the opposing side of theenlarged head portion 435). In this regard, the engagement between theflange 753 and the enlarged head portion 435 may serve to resistrelative movement between the alignment pin 429 and the alignment barrel740 and thus between the connectors 428, 432 (e.g., in a direction thatwould otherwise tend to disengage the connectors 428, 432, such as dueto vibrations, shocks, and/or the like), in the absence of a userintending to disengage the connectors 428, 432 (e.g., such as during aFRU hot-swap operation).

While engagement between the enlarged head portion 435 of the alignmentpin 429 and the flange 753 of the alignment barrel 740 has beendiscussed as a manner of ensuring electrically engagement between theconnectors 428, 432, other arrangements of doing the same are alsoenvisioned and encompassed herein. For instance, the flange 753 of thealignment barrel 740 may be configured to snap into or otherwise enter agroove or the like disposed about an outer circumference of thealignment pin 429. Furthermore, the enlarged head portion 435 (or otherfeature) and flange 753 (or other feature) may be disposed at locationson the alignment pin 429 and alignment barrel 740 other than at thoseshown in the figures. For instance, the enlarged head portion 435 couldbe disposed at a middle portion of the alignment pin 429 and the flange753 could be disposed inside the receiving bore 752 at a middle portionof the alignment barrel 740.

Turning now to FIGS. 21-22, another embodiment of an adapter 900 ispresented that is configured to allow a FRU 1012 to be inserted into areceiving bay of a computing rack (e.g., receiving bay 410 of computingrack 404 of FIG. 12) and substantially seamlessly electronicallydiscovered by management services software of the computing rack by wayof blind mate interfacing between the adapter 900 and a frame arm 1016of a receiving bay of the computing rack. The adapter 900 may or may notbe utilized in racks in which the adapter 700 is being utilized withcorresponding frame arms 416. Broadly, the adapter 900 includes firstand second mounting portions 904 ₁, 904 ₂ (e.g., each including one ormore brackets) that are respectively configured to be non-movablysecured to opposing side portions 1013 ₁, 1013 ₂ of a FRU 1012 and anattachment portion 908 (e.g., one or more brackets) interconnecting thefirst and second mounting portions 904 ₁, 904 ₂. The attachment portion908 is configured to receive at least a first connector 1032 ₁ (e.g.,blind mate connector 132 of FIG. 4 or connector 432 of FIG. 16) to allowthe first connector 1032 ₁ to electrically interface with at least afirst corresponding connector 1028 ₁ (e.g., connector 128 of FIG. 4 orconnector 428 of FIG. 13) adjacent a rear of a receiving bay of acomputing rack (not shown, but similar to receiving bay 410 of rack 404of FIG. 12) as the FRU 1012 is being inserted into the receiving bay.

In one arrangement, the first and second mounting portions 904 ₁, 904 ₂may respectively include at least a first mounting member 912 ₁, 912 ₂(e.g., plate, flange, etc.) that is configured to be non-movably securedrelative to (e.g., directly or indirectly to) the first and second sideportions 1013 ₁, 1013 ₂ of the FRU 1012. For instance, the firstmounting members 912 ₁, 912 ₂ may be respectively rigidly secured (e.g.,via fasteners, nuts, and aligned holes, not labeled) to an insideportion of a pair of inner rail members (not labeled) of the same railassembly 1001 to which a respective frame arm 916 is secured (e.g.,where the frame arm 916 is secured to a pair of outer rail members 1050₁, 1050 ₂ of the rail assembly 1001 and the first mounting members 912₁, 912 ₂ are secured to the pair of inner rail members of the same railassembly 1001). In this regard, rigid mounting of the inner rail membersto the side portion 1013 ₁, 1013 ₂ of the FRU 1012 (e.g., similar to howinner rail member 454 may be rigidly secured to the side portion 413 ofFRU 412 as discussed previously) serves to non-movably or rigidly securethe adapter 900 to the FRU 1012. In another arrangement, the mountingportions 904 ₁, 904 ₂ may additionally or alternatively includeadditional mounting members (e.g., plate, flange, etc., not shown)configured to be non-movably secured to the side portions 1013 ₁, 1013 ₂of the FRU 1012 for increased stability of the system.

With continued reference to FIGS. 21-22, the attachment portion 908 mayinclude an attachment member 928 (e.g., plate, bracket, flange, etc.)rigidly interconnecting the first and second mounting portions 904 ₁,904 ₂ that includes at least a first receiving aperture extendingtherethrough (not shown, but similar to receiving aperture 732 in FIG.14, albeit arranged in a horizontal direction in the embodiment of FIGS.21-22). The first receiving aperture may be sized and configured tofixably receive the first connector 1032 ₁ therein so as to face a frontportion (not shown) of the first connector 1032 ₁ towards a frontportion (not shown) of the first connector 1028 ₁ of a correspondingframe arm 1016 during insertion of the FRU 1012 into the receiving bayof the rack (e.g., one of the receiving bays 410 of rack 404). It isnoted that FIGS. 21-22 illustrate the adapter 900 being engaged with theframe arm 1016.

For instance, the first connector 1032 ₁ may include one or moreflexible tangs, clips or the like (not shown) that are adapted to snappast an inner wall of the first receiving aperture and thereby lock ornon-movably fix the first connector 1032 ₁ to the attachment portion 908and thus to the FRU 1012 (i.e., when the mounting portion 904 isnon-movably fixed to or at least relative to the FRU 1012). However,other manners of securing the first connector 1032 ₁ to the attachmentportion 908 are also envisioned and encompassed herein. In onearrangement, the attachment member 928 may be rigidly secured to thefirst mounting members 912 ₁, 912 ₂ of the first and second mountingportions 904 ₁, 904 ₂ in any appropriate manner (e.g., threadedconnections, welding, etc.). In another arrangement, a single piece ofmaterial may be appropriately formed and/or shaped to create the firstand second mounting portions 904 ₁, 904 ₂ and attachment portion 908.

The first and second mounting portions 904 ₁, 904 ₂ may collectivelyspace the attachment portion 908 a distance 924 from a rear portion 1014of the FRU 1012 to advantageously provide room for one or more cables,wires, and/or the like (not shown) that electrically connect power,serial, and network ports (not labeled) adjacent the rear portion 1014of the FRU 1012 to a rear portion 1033 of the first connector 1032 ₁secured to the attachment portion 908 of the adapter 900. In onearrangement, the adapter 900 may include a base or tray 960appropriately secured to first and second mounting portions 904 ₁, 904 ₂and/or attachment portion 908. In any case, the first and secondmounting portions 904 ₁, 904 ₂ and attachment portion 908 (and tray 960if included) may collectively form at least a partial housing forcontaining the plurality of cables/wires/etc. electricallyinterconnecting the first connector 1032 ₁ and the ports adjacent therear portion 1014 of the FRU 1012.

In one arrangement, the attachment member 928 may include at least asecond receiving aperture (not shown) sized and configured to receive asecond connector 1032 ₂ (e.g., blind-mate connector) so as to face afront portion (not shown) of the second connector 1032 ₂ towards a frontportion (not shown) of a second connector 1028 ₂ of the frame arm 1016during insertion of the FRU 1012 into the receiving bay of the rack.Provision of the second connectors 1032 ₂, 1028 ₂ advantageously allowsfor blind-mate electrical connection between one or more additionalports of the FRU 1012 and additional cables/wires/networks of the rackand/or the like. In one arrangement, one or more cables/wires (notshown) may be electrically connected between high speed network ports970 (e.g., Ethernet, RJ45) of the FRU 1012 and the second connector 1032₂ of the adapter 900. For instance, the high speed network ports 970 maybe utilized for actual data (e.g., signal) communications between theFRU 1012 and other devices and/or processes (e.g., other FRUs1012/412/112 within rack 404/104, devices or processes outside of rack404, etc.) as opposed to for management communications between and amongthe frame center (e.g., frame center 120), frame arms 116/416/1016, FRUs112/412/1012, etc.

The frame arm 1016 may generally have a form factor in the width 405 andheight dimensions 407 (labeled in FIG. 12) substantially matching thatof the adapter 900. More particularly, the frame arm 1016 may include ahousing 1018 (e.g., housing 118) non-movably securable in anyappropriate manner relative to the pair of outer rail members 1050 ₁,1050 ₂ of the rail assembly 1001 of the particular receiving bay withinwhich an adapter 900 and FRU 1012 are translatably mounted. As just oneexample, the housing 1018 may include first and second mounting portions1104 ₁, 1104 ₂ including respective pairs of grooves 1019 (see FIG. 23)that are configured to receive corresponding pairs of flanges (notshown) of the outer rail members 1050 ₁, 1050 ₂. In this regard, thehousing 1018 can be slid along or relative to the outer rail members1050 ₁, 1050 ₂ to a desired location (e.g., adjacent a rear portion of areceiving bay) and then non-movably secured to the outer rail members1050 ₁, 1050 ₂ in any appropriate manner (e.g., via tightening a bolt(not shown) extending through opposing side portions of the housing 1018against the outer rail members 1050 ₁, 1050 ₂). Other manners ofsecuring the housing 1018 to the rack adjacent a rear portion of thereceiving bay are also envisioned and encompassed within the scope ofthe present disclosure.

The housing 1018 may also include a base or tray 1090 rigidly secured inany appropriate manner between the first and second mounting portions1104 ₁, 1104 ₂ to which a PCB 1022 (e.g., PCB 122, 422) may be secured,such as via passing fasteners 1017 through apertures (not shown) in thePCB 1022 and into apertures (not shown) in the tray 1090 of the housing1018. The PCB 1022 may have a memory storing location data of the framearm 1016 within the frame (e.g., frame 400), serial to I²C conversionlogic, LEDs, and the like (not labeled), similar to the PCB 122 in FIG.4 and PCB 422 in FIG. 13. As shown, the first connector 1028 ₁ may beelectrically connected and secured in any appropriate manner to the PCB1022 and adapted to align and electrically interface with the firstconnector 1032 ₁ of the adapter 900 to facilitate electrical connectionbetween the respective FRU 1012, the frame center, and one or more PDUsvia a fixed interconnect topology (e.g., fixed interconnect topology424). More specifically, at least one I²C cable or line (e.g., I²C line20 of FIG. 4) may be electrically connected between the frame center andthe PCB 1022 (e.g. to an I²C data bus of the PCB 1022), at least onenetwork cable or line (e.g., network line 24 of FIG. 4) may beelectrically connected between the frame center and pins/contacts (notshown) adjacent a rear portion 1070 of the first connector 1028 ₁ (andthus may “pass-through” the PCB 1022), and at least one power line orcable (e.g., power lines 28, 32 of FIG. 4) may be electrically connectedbetween one or more PDUs (e.g., PDUs 508, 512) and pins/contactsadjacent the rear portion 1070 of the connector 1028.

The second connector 1028 ₂ may also be secured in any appropriatemanner to the frame arm 1016 (e.g., to the tray 1090) and adapted toalign and electrically interface with the second connector 1032 ₂ of theadapter 900 to facilitate electrical connection (e.g., actual datacommunications) between the respective FRU 1012 and one or more networksvia the fixed interconnect topology (e.g., fixed interconnect topology424) and/or other cables/wires. For instance, one or more network (e.g.,Ethernet) cables (e.g., not shown) may be appropriately electricallyinterconnected to a rear portion of the second connector 1028 ₂ so thatan electrical (e.g., data) connection is established between the FRU1012 and one or more networks (e.g., Internet, WAN, LAN) uponinterfacing of the second connectors 1032 ₂, 1028 ₂.

In one arrangement, the housing 1018 may additionally include acorresponding attachment portion 1120 configured to substantially abutthe attachment portion 908 of the adapter 900 upon full insertion of theFRU 1012 into the receiving bay, where the attachment portion 1120includes respective first and second receiving apertures (not shown) forrespective receipt and mounting (e.g., via clips or the like) of thefirst and second connectors 1028 ₁, 1028 ₂. In this regard, the adapter900 and frame arm 1016 may be substantial mirror images of each other(e.g., where the adapter 900 and frame arm 1016 have respective trays960, 1090, attachment portions 908, 1120, first and second mountingportions 904 ₁, 904 ₂ and 1104 ₁, 1104 ₂, etc.).

In one embodiment, the frame arm 1016 may include at least onemechanical connector or alignment component such as first and secondalignment pins 1029 ₁, 1029 ₂ that are configured to be received inrespective corresponding mechanical connectors or alignment componentssuch as first and second alignment barrels (not shown, but similar toalignment barrel 740 of FIG. 16) of the adapter 900 of the FRU 1016. Forinstance, each of the first and second alignment pins 1029 ₁, 1029 ₂ maybe respectively disposed adjacent (e.g., directly adjacent, spacedlyadjacent, etc.) the first and second connectors 1028 ₁, 1028 ₂ whileeach of the first and second alignment barrels may be respectivelydisposed adjacent (e.g., directly adjacent, spacedly adjacent, etc.) thefirst and second connectors 1032 ₁, 1032 ₂. As discussed previously inrelation to the alignment pin 429 and alignment barrel 740 of FIGS.13-19, receipt of each of the first and second alignment pins 1029 ₁,1029 ₂ in the respective first and second alignment barrels duringinsertion of the FRU 1012 into a receiving bay towards the frame arm1016 facilitates precise alignment between the pins/contacts of therespective connectors 1028 ₁/1032 ₁, 1028 ₂/1032 ₂.

In the event that the connectors 1028 ₁/1032 ₁, 1028 ₂/1032 ₂ haverespective alignment posts and openings (not labeled, but similar toalignment posts/openings 475, 476 in FIGS. 13 and 16), each alignmentpin 1029/alignment barrel 940 combination may be considered a “primary”alignment mechanism (e.g., that serves to perform initial alignment ofthe pins/contacts of the corresponding connectors 1028 ₁/1032 ₁, 1028₂/1032 ₂) while each alignment post/alignment opening combination may beconsidered a “secondary” alignment mechanism (e.g., that serves toperform more fine-tuned alignment of the pins/contacts of thecorresponding connectors 1028 ₁/1032 ₁, 1028 ₂/1032 ₂). In someembodiments, the housing 1018 of the frame arm 1016 may include a cover1061 (shown in FIG. 23; removed from FIGS. 21-22 in the interest ofclarity) attached to the first and second mounting portions 1104 ₁, 1104₂ and/or attachment portion 1120 for protecting the PCB 1022 andconnectors 1028 ₁, 1028 ₂, increasing the rigidity of the frame arm1016, and/or the like.

The method 800 of FIG. 20 may be applicable to the adapter 900/frame arm1016 combination in a manner similar to that discussed previously inrelation to the adapter 700/frame arm 416 combination. For instance, themethod 800 may include inserting 804 ends (not labeled) of the pair ofinner rail members of FRU 1012 into channels (not labeled) of the pairof outer rail members 1050 ₁, 1050 ₂ of a receiving bay (e.g., receivingbay 410) of a computing rack (e.g., computing rack 404), advancing 808(e.g., sliding, moving, etc.) the FRU 1012 towards the rear portion ofthe receiving bay, mechanically aligning 812 the electrical connector1032 ₁, 1032 ₂ of the FRU 1012 with the corresponding electricalconnector 1028 ₁, 1028 ₂ of the frame arm 1016 (e.g., via receiving thealignment pins and/or posts within the alignment barrels and/oropenings), and electrically interfacing 828 the connectors 1028 ₁/1032₁, 1028 ₂/1032 ₂ after or upon mechanical alignment 812 of theconnectors 1028 ₁/1032 ₁, 1028 ₂/1032 ₂. At this point, the FRU 1012 maybe substantially automatically and/or seamlessly discovered by the framecenter (e.g., frame center 120 of FIG. 1) and/or frame manager (e.g.,frame manager 168 of FIG. 1) of the computing rack via the fixedinterconnect topology 424, the frame center and/or frame manager mayconduct OOB management of the FRU 1012, FRU hot-swap/removal requestsmay be generated by the frame arm 1016 (e.g., upon depression of acorresponding button on the frame arm 1016) and passed to the framecenter for processing, and/or the like, all as discussed previously.

In one arrangement, the adapter 900 and frame arm 1016 may be utilizedfor “1U” FRUs 1012 as the adapter 900 and frame arm 1016 may beconfigured to have reduced form factors in the height dimension 407(labeled in FIG. 12) of the rack 404, such as due to the adapter 900 andframe arm 1016 being configured to orient the various connectors 1032,1028 (e.g., the longest dimension of the connectors 1032, 1028) alongthe width dimension 405 of the rack 404 (i.e., as opposed to along theheight dimension 407 as do the adapter 700 and frame arm 416 of FIGS.12-19). For instance, the adapter 900 and frame arm 1016 may be utilizedfor 1U FRUs 1012 while the adapter 700 and frame arm 416 may be utilizedfor 2U FRUs 412 which may or may not be utilized in the same rack 404.However, it is envisioned that each adapter 900/frame arm 1016 andadapter 700/frame arm 416 combination may be utilized with FRUs of otherform factors (e.g., 1U, 2U, 3U, etc.).

In some situations, electromagnetic interference (EMI) may be generatedas a result of the electrical connection of the high speed network ports970 (e.g., Ethernet, RJ45) of the FRU 1012 and the second connector 1032₂ of the adapter 900. In this regard, the housing created by the firstmounting portion 904 ₁, second mounting portion 904 ₂, and attachmentportion 908 may serve as a “cage” that serves to attenuate or otherwisecontrol the generated EMI. Furthermore, one or more portions of theadapter 900 and/or frame arm 1016 (e.g., the trays 960, 1090; theattachment portions 908, 1120; and/or the like) may include a number ofperforations or the like therethrough for facilitating air circulation,weight reductions, and/or the like.

Turning now to FIGS. 24-27, various views of another example of a smartcomputing frame 1200 (e.g., frame 100 of FIG. 1) mounted within acomputing or storage rack 1300 are illustrated that may be used toefficiently manage a wide variety of FRUs such as rack-mount servers,data storage devices, backup power modules, and/or the like of one ormore form factors such as 1U, 2U, and/or the like installed in thestorage rack 1300. Broadly, the frame 1200 includes a plurality ofbackplane nodes 1204 (e.g., frame arms) rigidly or non-movably mountableadjacent respective rear portions of receiving bays of the storage rack1300 for electrical interface with adapters 1600 of respective FRUs 1312installed into the receiving bays to facilitate OOB management of theFRUs 1312 via a fixed interconnect topology (not shown, but see fixedinterconnect topology 124 of FIGS. 1 and 4) that electrically connectseach of the FRUs 1312 to a central management controller of the frame1200 (not shown, but see frame center 120 of FIGS. 1 and 5) via thebackplane nodes 1204 and the FRU adapters 1600.

Before discussing the frame 1200 in more detail, reference will be madeto the storage rack 1300 of FIGS. 24-27 to provide an example of onerepresentative environment in which the frame 1200 may be implemented.It is to be understood though that the disclosed frame 1200 may beimplemented in various other shapes, configurations and sizes of storageracks for electronic devices and/or FRUs, all of which are encompassedherein. Broadly, the storage rack 1300 may include a pair of spacedfront vertical support posts or pillars 1304 and a pair of spaced rearvertical support posts or pillars 1308 spaced from the front verticalsupport pillars 1304 and that extend upward from a floor or otherplatform (not shown) to form an interior storage space in which the baysof the storage rack 1300 are disposed for receiving respective FRUs1312.

Each of the front and rear vertical pillars 1304, 1308 may be operableto receive and/or engage with a plurality of pairs of first railassemblies 1400 (e.g., outer rail members 450 of FIG. 13, outer railmembers 1050 of FIG. 21, etc.) that generally define the bays forstructurally supporting the FRUs 1312, where each pair of first railassemblies 1400 is configured to rigidly connect the front and rearvertical pillars 1304, 1308. Each first rail assembly 1400 may generallyinclude a body member or portion 1404 rigidly attachable to front andrear vertical pillars 1304, 1308 such as via respective mounting tabs(not labeled) attached to the front and rear vertical pillars 1304,1308. For instance, each body member 1404 may be in the form of firstand second rail members 1416, 1420 that are slidably attached to eachother to accommodate differences in front to rear pillar spacing amongdifferent storage racks and that are lockable to inhibit sliding betweenthe first and second rail members 1416, 1420 once the mounting tabs aremounted on the front and rear pillars 1304, 1308. In any case, the bodymember 1404 may have first and second opposite edge or edge portions1408, 1412 along which a corresponding second rail assembly 1500 (e.g.,to which a corresponding FRU 1312 and FRU adapter 1600 are non-movablyattached) is configured to slide. In one arrangement, the pairs of firstrail assemblies 1400 may be those described in a U.S. patent applicationentitled “ADJUSTABLE SNAP-IN RAIL ASSEMBLY FOR STORAGE RACK,” identifiedby client matter no. ORA150997-US-NP, filed with the U.S. Patent andTrademark Office on the same day as the present application, andassigned to the Assignee of the present application, the entire contentsof which are incorporated herein by reference as if set forth in full.

Each pair of first rail assemblies 1400 is configured to receive andguide a FRU 1312 into the rack such that when fully loaded, a rearportion of the FRU 1312 is adjacent or proximate the rear pillars 1308and the front portion of the FRU 1312 is adjacent or proximate the frontpillars 1304. The storage rack 1300 may be further defined by anyappropriate arrangement of other vertical and horizontal members 1316,1320, paneling or wall members (not shown), and the like. The storagerack 1300 may also include a front access opening 1324 through which theFRUs 1312 may be refracted and reinserted, and a rear access opening1328 through which necessary connections may be made to the backplanenodes 1204 and/or FRUs 1312. Access doors (not shown) may be providedover the front and rear access openings 1324, 1328 to limit immediateaccess to the interior of the storage rack 1300. Grills or otherperforations may be included in any appropriate portion of the storagerack 1300 to enhance airflow therethrough and the various components ofthe storage rack 1300 may be formed of metal, plastic, composites,and/or the like.

In some arrangements, the rear pillars 1308 may be set back from therear access opening 1328 of the rack 1300 such that a space 1332 isdefined between the rear pillars 1308 and the rear access opening 1328for the passage of cabling (e.g., fixed interconnect topology 124, notshown), the mounting of the backplane nodes 1204, etc. For instance, theplurality of first rail assemblies 1400 may extend into the space 1332for support of the backplane nodes 1204.

In any case, each backplane node 1204 may generally include a housing1208 (e.g., a first housing) rigidly interconnecting a first railassembly 1400 ₁ of a respective one of the plurality of pairs of firstrail assemblies 1400 to an opposite second rail assembly 1400 ₂ of therespective one of the plurality of pairs of first rail assemblies 1400.Broadly, the housing 1208 may be configured to contain or support one ormore PCBs (e.g., PCB 122 of FIG. 4) including any appropriatearrangement of circuitry that includes memory (e.g., memory 136 ofFigure) storing the location data (e.g., location data 141 of FIG. 1) ofthe backplane node 1204 (e.g., frame arm 116) in the frame 1200 asdiscussed previously. The housing 1208 is also configured to contain orsupport one or more first blind mate connectors 1212 that are configuredto respectively interface with one or more second blind mate connectors1612 of a corresponding second housing 1608 of a respective FRU adapter1600 to electrically interconnect a corresponding FRU 1312 to the framecenter (e.g., central management controller or frame center 120 of FIG.1), PDUs (e.g., PDUs 508, 512 of FIG. 2), etc.

As shown in FIGS. 27-32, the housing 1208 may include first and secondspaced side members 1216, 1220 that are respectively rigidlyinterfaceable with the first and second rail assemblies 1400 ₁, 1400 ₂of a respective pair of first rail assemblies 1400 and an attachmentportion 1224 that rigid interconnects the first and second side members1216, 1220 so as to be non-movable relative to the first and second sidemembers 1216, 1220. As used herein, “rigidly interfaceable” means thatthe first and second side members 1216, 1220 are configured to be placeor disposed against, near or adjacent the first and second railassemblies 1400 ₁, 1400 ₂ and thereafter non-movable relative to thefirst and second rail assemblies 1400 ₁, 1400 ₂ without necessarilymeaning that the first and second side members 1216, 1220 are directlyrigidly attached to the first and second rail assemblies 1400 ₁, 1400 ₂(e.g., such as via extending fasteners through the side members 1216,1220 and into the first and second rail assemblies 1400 ₁, 1400 ₂).

For instance, the first and second side members 1216, 1220 may be in theform of rail members, brackets, etc. that are slidably receivable alongthe body members 1404 of the first and second rail assemblies 1400 ₁,1400 ₂ (e.g., during initial installation of the backplane node 1200 inthe rack 1300) and then rigidly interfaceable to the first and secondrail assemblies 1400 ₁, 1400 ₂ (e.g., such that the first and secondside members 1216, 1220 are generally parallel to the body members 1404of the first and second rail assemblies 1400 ₁, 1400 ₂). In onearrangement, each of the first and second rail assemblies 1400 ₁, 1400 ₂may include first and second spaced containment members 1424, 1428(e.g., flanges, brackets, sheet members, etc.) respectively extendingaway from (e.g., rigidly/non-movably attached or connected to) the firstand second edges 1408, 1412 of the body member 1404 in a directiontowards an inside of the rack 1300 and defining a receiving space 1432therebetween for receiving the housing 1208 (e.g., the first and secondside members 1216, 1220 and a portion of the attachment portion 1224).For instance, the first and second containment members 1424, 1428 mayextend perpendicularly away from the first and second edges 1408, 1412so that the space 1432 is approximately equal to (e.g., slightly greaterthan) a height 1228 (labeled in FIG. 28b ) of the housing 1208. In onearrangement, the first and second containment members 1424, 1428 may bedisposed in the space 1332 between the rear vertical pillars 1308 andrear opening 1328 of the storage rack 1300.

With reference again to the housing 1208 of the backplane node 1204, theattachment portion 1224 rigidly interconnects the first and second sidemembers 1216, 1220 and is configured to rigidly (e.g., non-movably)support the one or more first blind mate connectors 1212. Stateddifferently, the attachment portion 1224 is specifically configured toposition the one or more first blind mate connectors 1212 so that uponthe backplane node 1204 being rigidly secured to or relative to arespective pair of first rail assemblies 1400 as disclosed herein, theone or more second blind mate connectors 1612 of a FRU adapter 1600non-movably secured to a FRU 1312 can substantially seamlessly interfaceand mate with the corresponding one or more first blind mate connectors1212 of the backplane node 1204 as the FRU 1312 is being inserted intothe bay generally defined by the respective pair of first railassemblies 1400.

In one arrangement, the attachment portion 1224 may include a base ortray 1232 (e.g., bracket, sheet member, etc.) that is rigidly attachedbetween (e.g., and/or otherwise non-movable relative to) the first andsecond side members 1216, 1220 and that is configured to serve as aplatform for one or more of the first blind mate connectors 1212; a PCBincluding circuitry with frame location data, serial to I2C translationlogic, and/or the like; cabling (not shown, but see fixed interconnecttopology 424 of FIG. 12) interconnected to the one or more of the firstblind mate connectors 1212; installation or use labels, and/or the like.For instance, the tray 1232 may include first and second opposite ends(not labeled) rigidly attached to (or otherwise non-movable relative to)the first and second side members 1216, 1220 along with opposite top andbottom surfaces (not labeled). In one arrangement, the tray 1232 mayinclude cutouts 1242 (e.g., or other openings) therethrough for thepassage of cables of the fixed interconnect topology 424. When aplurality of backplane nodes 1204 are mounted in a storage rack in avertically stacked manner, the various cutouts 1242 of the backplanenodes 1204 may align in the vertical direction providing elongatedpassageways for the fixed interconnect topology 424.

In one arrangement, the PCB may be contained within a housing of a first1212 ₁ of the first blind mate connectors (e.g., where the circuitry ofthe PCB is appropriately electrically connected with an interfaceportion 1244 of the first blind mate connector 1212 ₁ that is configuredto electrically interface with a corresponding interface portion 1644 ofa corresponding first of one or more second blind mate connectors 1612of the FRU adapter 1600 (e.g., and thus with an OOB processor of the FRU1312). For instance, the PCB may also be electrically interfaceable withthe fixed interconnect topology 424/124 (e.g., see FIGS. 1 and 12) andthus other FRUs 1312 in the frame 1300 and the frame center via one ormore ports 1248.

In any event, the attachment portion 1224 may also include a divider orwall 1236 extending away or otherwise protruding from the top surface ofthe tray 1232 (e.g., perpendicularly) through which interface portions1244 of the one or more first blind mate connectors 1212 are configuredto extend for mating with the corresponding one or more second blindmate connectors 1612 of the FRU adapter 1600. In one arrangement, thewall 1236 may extend from and rigidly interconnect the first and secondside portions 1216, 1220. In any case, the wall 1236 may include aplurality of receiving openings 1240 therethrough for receiving thecorresponding interface portions 1244 of the one or more first blindmate connectors 1212. For instance, each of the one or more first blindmate connectors 1212 may include one or more flexible tangs, clips orthe like (not shown) that are adapted to snap past inner walls of thereceiving openings 1240 and thereby lock or otherwise non-movably fixthe first blind mate connectors 1212 to the wall 1236 and thus to thehousing 1208 of the backplane node 1204. However, other manners ofsecuring the first blind mate connectors 1212 to the wall 1236 are alsoenvisioned and encompassed herein (e.g., threaded fasteners, etc.).

In one arrangement, the tray 1232 may include one or more guide featuresthat facilitate insertion of the interface portion 1244 of one or moreof the first blind mate connectors 1212 into the receiving apertures1240 of the wall 1236. As an example, the tray 1232 may include firstand second spaced guide members 1252, 1256 therein or thereon (see FIGS.27 and 30) that are configured to slidably receive the first 1212 ₁ ofthe first blind mate connectors 1212 therebetween along the top surfaceof the tray 1232 and guide the interface portion 1244 of the same into acorresponding one of the receiving apertures 1244. For instance, thefirst and second guide members 1252, 1256 may be in the form of firstand second brackets protruding from the top surface of the tray 1232 andgenerally spaced by a distance substantially equal to a width of thefirst 1212 ₁ of the first blind mate connectors 1212. For instance, thefirst and second guide members 1252, 1256 may be respective portions ofthe tray that have been bent or otherwise appropriately manipulatedupward. As another example, the first and second guide members 1252,1256 may be separate pieces that are appropriately attached to the tray1232 (e.g., via fasteners, rivets, etc.).

Furthermore, the first and second guide members 1252, 1256 may beappropriately positioned on the top surface off the tray 1232 relativeto the corresponding receiving opening 1240 through the wall 1236 sothat the interface portion 1244 of the first 1212 ₁ of the first blindmate connectors 1212 substantially automatically enters thecorresponding receiving opening 1240 as a user continues to slide thefirst 1212 ₁ of the first blind mate connectors 1212 between the firstand second guide members 1252, 1256 towards the wall 1236. In onearrangement, a distance between the first and second guide members 1252,1256 may increase along a portion of the lengths of the first and secondguide members 1252, 1256 in a direction away from the correspondingreceiving opening 1240 to facilitate initial receipt of the first 1212 ₁of the first blind mate connectors 1212 between the first and secondguide members 1252, 1256. In one embodiment, the first and second guidemembers 1252, 1256 may be spring-loaded members that are configured toexert at least a slight force against outside side walls of the first1212 ₁ of the first blind mate connectors 1212.

In one arrangement, the attachment portion 1224 of the housing 1208 mayinclude one or more features or components that allow for a constrainedamount of “floating” of the interface portion 1244 of one or more of thefirst blind mate connectors 1212 relative to its corresponding receivingaperture 1240 (e.g., relative to the wall 1236) to facilitate mating ofthe interface portion 1244 with that of a corresponding one of thesecond blind mate connectors 1612 of the FRU adapter 1600. For instance,the wall 1236 may include first and second apertures 1260, 1264therethrough on opposite sides of a corresponding receiving aperture1240 that are configured to slidably receive first and second pins 1268,1270 extending from the housing of the first 1212 ₁ of the first blindmate connectors 1212 on opposite sides of the interface portion 1244.See FIGS. 28a, 28b and 29.

More specifically, at least one of the first and second apertures 1260,1264 may be in the form of a slot (i.e., not a circle) that allows thecorresponding one of the first and second pins 1268, 1270 to slidetherein when the interface portion 1244 is received in the correspondingreceiving aperture 1240 (e.g., via the interface portion 1244essentially slightly pivoting about the other of the first and secondpins 1268, 1270). For instance, the first and second apertures 1260,1264 may be in the form of respective first and second slots that extendalong respective first and second longitudinal axes 1262, 1266. In onearrangement, the first and second longitudinal axes 1262, 1266 may besubstantially perpendicular to each other. In the event the attachmentportion 1224 includes features that allow for the above-notedconstrained floating of the interface portion 1244 of one or more of thefirst blind mate connectors 1212, the corresponding receiving aperture1240 may have dimensions larger than those of the interface portion 1244to allow for such floating.

In one arrangement, the housing 1208 of the backplane node 1204 mayfurther include a cover member 1272 (see FIG. 28a ) securable in anyappropriate manner to the attachment member 1224 to at least partiallyconceal and protect the one or more blind mate connectors 1212, PCB,cabling, etc. contained inside the housing 1208. For instance, the covermember 1272 may include first and second portions 1274, 1276 configuredto be respectively opposed to the tray 1232 and wall 1236 when securedto the attachment member 1224 so as to conceal the above-discussedcomponentry in a box-like structure. As shown, the first portion 1274may include cutouts 1277 corresponding to the cutouts 1242 of the tray1232 to facilitate passage of cabling through the housing 1208.

To mount each backplane node 1204 to a corresponding pair of first railassemblies 1400 (e.g., first and second rail assemblies 1400 ₁, 1400 ₂),the first and second side portions 1216, 1220 of the housing 1208 mayinitially be respectively inserted between the first and second railassemblies 1400 ₁, 1400 ₂ (e.g., wall 1236 first) and the housing 1208may be appropriately rigidly (i.e., non-movably) secured to the firstand second rail assemblies 1400 ₁, 1400 ₂. For instance, the first andsecond side portions 1216, 1220 of the housing 1208 may be respectivelyinserted into the receiving spaces 1432 between the first and secondspaced containment members 1424, 1428 of the first and second railassemblies 1400 ₁, 1400 ₂. In one arrangement, respective guide slots1290 disposed on a portion of the housing 1208 (e.g., on the firstportion 1274 of the cover 1272) may be configured to receive an outeredges of the first containment members 1424 of the first and second railassemblies 1400 ₁, 1400 ₂ to facilitate insertion of the housing 1208into the receiving spaces 1432 between the body members 1404 of thefirst and second rail assemblies 1400 ₁, 1400 ₂.

Thereafter, the housing 1208 may be rigidly (i.e., non-movably) securedto the first and second rail assemblies 1400 ₁, 1400 ₂ in anyappropriate manner. In one arrangement, the tray 1232 of the housing1208 may be rigidly secured to the first and/or second spacedcontainment members 1424, 1428 of the first and second rail assemblies1400 ₁, 1400 ₂ in any appropriate manner to rigidly or non-movablysecure the housing 1208 to and between the first and second railassemblies 1400 ₁, 1400 ₂. As just one example, the tray 1232 mayinclude one or more spring-loaded members 1278 (see FIGS. 27 and 30)that are configured to spring or snap into corresponding apertures 1436in the second containment members 1428 once the housing 1208 has reacheda position on the first and second rail assemblies 1400 ₁, 1400 ₂whereby the one or more blind mate connectors 1212 can appropriatelyinterface with the one or more corresponding second blind mateconnectors 1612 of the FRU adapter 1600 (as will be discussed in moredetail below). For instance, each spring loaded member 1278 may includea barrel 1282 rigidly secured to a top of the tray 1232 along with aspring loaded pin 1284 that is reciprocally mounted in a passageway ofthe barrel 1282. The spring-loaded member 1278 may be configured to biasthe pin 1284 through an aperture in the tray 1232 so as to protrudebeyond a lower surface of the tray 1232. See FIG. 28 b.

During insertion of the housing 1208 into the receiving spaces 1432 ofthe first and second rail assemblies 1400 ₁, 1400 ₂, the end of the pin1284 protruding beyond the lower surface of the tray 1232 may initiallycontact a leading edge of the second containment member 1428. Continuedurging of the housing 1208 into and through the receiving spaces 1432may serve to push the pin 1284 upwardly in the barrel 1282 against thespring force until the pin 1284 has just cleared the lower surface ofthe tray 1232. After at least some continued urging of the housing 1208,the spring eventually forces the pin 1284 back down the barrel past thelower surface of the tray 1232 and into and/or through the correspondingaperture 1436 in the second containment member 1428 to lock the housing1208 against movement relative to the first and second rail assemblies1400 ₁, 1400 ₂. In one arrangement, the end of the pin 1284 may betapered to facilitate the automatic lifting or withdrawal of the pin1284 in the barrel 1282 during insertion of the housing 1208.

One or more other spring loaded members 1278 may be additionally oralternatively appropriately located on the housing 1208 to engage withcorresponding apertures in the first and/or second rail assemblies 1400₁, 1400 ₂ (e.g., on the first and second side members 1216, 1220 toengage with corresponding apertures in the body members 1404 of thefirst and/or second rail assemblies 1400 ₁, 1400 ₂). To remove thehousing 1208 from the rack 1300, a user may lift up (or out) on thespring-loaded pins 1284 to clear the ends of the pins 1284 just past thelower surface of the tray 1232 (e.g., or outside surface of the firstand second side members 1216, 1220) and the pull or urge the housing1208 away from the inside of the rack 1300. In some arrangements, springloaded members 1278 may be located on the first and second railassemblies 1400 ₁, 1400 ₂ and corresponding apertures may be disposed inthe housing 1208. Either before or after the housing 1208 is mounted tothe respective pair of first rail assemblies 1400, the one or more firstblind mate connectors 1212 may be appropriately secured to mounted tothe attachment portion 1224 of the housing as discussed above and thefixed interconnect topology 424 (e.g., see FIG. 12) may be appropriatelyelectrically connected to the one or more first blind mate connectors1212.

As discussed above, each FRU adapter 1600 is broadly configured tosubstantially seamlessly electrically interface a corresponding FRU 1312with the frame 1200 (e.g., with a central management controller or framecenter, with a PDU, etc.) when one or more second blind mate connectors1612 of the FRU adapter 1600 mate with the one or more correspondingfirst blind mate connectors 1212 of a corresponding backplane node 1200as the FRU 1312 is slid into a corresponding receiving back of thestorage rack 1300. Broadly, FRU adapter 1600 (see FIGS. 25 and 33-36)may generally include a housing 1608 (e.g., a second housing) rigidlyinterconnecting a first rail assembly of a respective one of theplurality of pairs of second rail assemblies 1500 (e.g., inner railmembers 454 of FIGS. 14 and 18) to an opposite second rail assembly (notshown) of the respective one of the plurality of pairs of second railassemblies 1500. Stated differently, each housing 1608 and a respectiveFRU 1312 are configured to be rigidly or non-movably secured to thefirst and second rail assemblies of a respective pair of second railassemblies 1500. In this regard, upon slidable engagement of the firstand second rail assemblies of a respective pair of second railassemblies 1500 with the first and second rail assemblies 1400 ₁, 1400 ₂of a respective pair of first rail assemblies 1400 of a particularreceiving bay of the rack 100, the FRU 1312 and corresponding FRUadapter 1600 may be slidable into and out of the bay as a single unit.

Each housing 1608 may be configured to contain or support one or moresecond blind mate connectors 1612 that are configured to respectivelyinterface with the one or more first blind mate connectors 1312 of acorresponding housing 1308 of a respective backplane node 1300 toelectrically interconnect a corresponding FRU 1312 to the frame center(e.g., central management controller or frame center 120 of FIG. 1),PDUs (e.g., PDUs 508, 512 of FIG. 2), etc. As shown, the housing 1608may generally include first and second spaced side members 1616, 1620that are respectively rigidly interfaceable with the first and secondrail assemblies of a respective pair of second rail assemblies 1500 andan attachment portion 1624 that rigid interconnects the first and secondside members 1616, 1620 so as to be non-movable relative to the firstand second side members 1616, 1620.

In one arrangement, the first and second side members 1616, 1620 may bein the form of rail members, brackets, etc. that are rigidly ornon-movably connectable to the body members (not labeled) of the firstand second rail assemblies of the respective pair of second railassemblies 1500. For instance, respective threaded fasteners 1626extending through the first and second side members 1616, 1620 may bethreaded into the body members of the first and second rail assembliesof the respective pair of second rail assemblies 1500. Additionally oralternatively, respective spring-loaded members (e.g., spring loadedmembers 1278) may be respectively mounted on the inside of the first andsecond side members 1616, 1620 to engage with corresponding apertures inthe first and second rail assemblies of the respective pair of secondrail assemblies 1500. While not shown, the first and second railassemblies of the respective pair of second rail assemblies 1500 may inone embodiment include first and second containment members (e.g.,similar to first and second containment members 1428, 1432 of first railassemblies 1400) that are configured to contain the second housing 1608.

The attachment portion 1624 rigidly interconnects the first and secondside members 1616, 1620 and is configured to rigidly (e.g., non-movably)support the one or more second blind mate connectors 1612. Stateddifferently, the attachment portion 1624 is specifically configured toposition the one or more second blind mate connectors 1612 so that uponinsertion of the pair of second rail assemblies 1500 into the receivingbay (e.g., so that the first and second rail assemblies of the pair ofsecond rail assemblies 1500 respectively slidably engage with the firstand second rail assemblies 1400 ₁, 1400 ₂ of the pair of first railassemblies 1400), the one or more second blind mate connectors 1612 cansubstantially seamlessly interface and mate with the corresponding oneor more first blind mate connectors 1212 of the backplane node 1204. Inone arrangement, the attachment portion 1624 may include a base or tray1632 (e.g., bracket, sheet member, etc.) that is rigidly attachedbetween (e.g., and/or otherwise non-movable relative to) the first andsecond side members 1616, 1620 and that is configured to serve as aplatform for one or more of the second blind mate connectors 1612,cabling electrically interfacing the FRU 1312 to the one or more secondblind mate connectors 1612 (not shown, but see cabling 736 of FIGS.16-19), installation or use labels, and/or the like.

The attachment portion 1624 may also include a divider or wall 1636extending away or otherwise protruding from the top surface of the tray1632 (e.g., perpendicularly) through which interface portions 1644 ofthe one or more second blind mate connectors 1612 are configured toextend for mating with the interface portions 1244 of the correspondingone or more first blind mate connectors 1212 of the backplane node 1204.In one arrangement, the wall 1636 may extend from and rigidlyinterconnect the first and second side portions 1616, 1620. In any case,the wall 1636 may include a plurality of receiving openings 1640therethrough for receiving the corresponding interface portions 1644 ofthe one or more second blind mate connectors 1612. For instance, each ofthe one or more second blind mate connectors 1612 may include one ormore flexible tangs, clips or the like (not shown) that are adapted tosnap past inner walls of the receiving openings 1640 and thereby lock orotherwise non-movably fix the second blind mate connectors 1612 to thewall 1636 and thus to the housing 1608 of the FRU adapter 1600.

However, other manners of securing the second blind mate connectors 1612to the wall 1636 are also envisioned and encompassed herein (e.g.,threaded fasteners, etc.). While not further discussed and/or shown, theattachment portion 1624 may include one more guide members (e.g., guidemembers 1252, 1256) on the tray 1632 for facilitating slidable insertionof one or more of the second blind mate connectors 1612 into thecorresponding receiving apertures 1640, one or more features orcomponents that allow for a constrained amount of “floating” of theinterface portion 1644 of one or more of the second blind mateconnectors 1612 relative to its corresponding receiving aperture 1640(e.g., relative to the wall 1636) to facilitate mating of the interfaceportion 1644 with that of a corresponding one of the first blind mateconnectors 1212 of the backplane node 1204, and/or the like.

To blind-matingly interconnect a FRU 1312 into the management network ofthe frame 1200, first and second rail assemblies of a respective pair ofsecond rail assemblies 1500 may be appropriately rigidly secured toopposite outside side surfaces of the FRU 1312 (e.g., similar to howinner rail members 454 are secured to side portions 413 of FRU 412 inFIG. 15). Furthermore, a respective FRU adapter 1600 may be rigidlysecured to the first and second rail assemblies of the respective pairof second rail assemblies 1500 as discussed above. A plurality of cablesor lines (not shown, but see cables 736 of FIGS. 16-19) may be used toelectrically interconnect various ports (e.g., power, serial, network,fiber optic, etc.) adjacent the rear portion of the FRU 1312 (e.g., seeports adjacent rear of FRU 1012 in FIGS. 21-22 and ports adjacent rearof FRU 412 in FIG. 16) to the one or more second connectors 1612 securedto the attachment portion 1624 of the housing 1608 of the FRU adapter1600.

The method 800 of FIG. 20 may be generally applicable to the FRU adapter1600/backplane node 1204 combination in a manner similar to thatdiscussed previously in relation to the adapter 900/frame arm 1016combination of FIGS. 21-23. For instance, the method 800 may includeinserting 804 ends (not labeled) of the first and second rail assembliesof the respective pair of second rail assemblies 1500 that are rigidlyattached to FRU 1312 and corresponding FRU adapter 1600 into channels(not labeled) of the first and second rail assemblies 1400 ₁, 1400 ₂ ofa respective pair of first rail assemblies 1400 that generally define areceiving bay in the storage rack 1300. The method 800 may then includeadvancing 808 (e.g., sliding, moving, etc.) the FRU 1312 towards therear portion of the receiving bay, mechanically aligning 812 the one ormore second blind mate connectors 1612 of the FRU adapter 1600 with theone or more first blind mate connectors 1212 of the backplane node 1204(e.g., via receiving alignment pins and/or posts of one of the FRUadapter 1600 or backplane node 1204 within alignment barrels and/oropenings of the other of the FRU adapter 1600 or backplane node 1204;not labeled, but similar to alignment pin 429 and alignment barrel 740discussed previously in relation to FIGS. 13-17), and electricallyinterfacing or mating 828 the one or more second blind mate connectors1612 of the FRU adapter 1600 with the one or more first blind mateconnectors 1212 of the backplane node 1204.

At this point, the FRU 1312 may be substantially automatically and/orseamlessly discovered by the central management controller (e.g., framecenter 120 of FIG. 1) and/or frame manager (e.g., frame manager 168 ofFIG. 1) of the frame 1200 via the fixed interconnect topology (e.g.,fixed interconnect topology 424, 724, the frame center and/or framemanager may conduct OOB management of the FRU 1312, FRU hot-swap/removalrequests may be generated by the backplane node 1204 (e.g., upondepression of a corresponding button on the backplane node 1204) andpassed to the frame center for processing, and/or the like, all asdiscussed previously. In the event that one or more of the first orsecond blind mate connectors 1212, 1612 are configured to float asdiscussed previously, the one or more first or second blind mateconnectors 1212, 1612 may be appropriately tightened down or otherwisenon-movably secured to its respective housing 1208, 1608. With referenceto the first 1212 ₁ of the one or more first blind mate connectors 1212,for instance, one or more fasteners 1294 (e.g., thumb screws) may bethreaded into respective apertures 1295 in or through the wall 1236 ofthe housing 1208 to limit such floating when the interface portion 1244of the first 1212 ₁ of the one or more first blind mate connectors 1212is mated with the interface portion 1644 of the corresponding first 1612₁ of the one or more second blind mate connectors 1612.

FIG. 37 presents a exploded view of the one or more first blind mateconnectors 1212 of the backplane node 1200 generally being aligned withcorresponding one or more second blind mate connectors 1612 of the FRUadapter 1600 (e.g., with rail assemblies, the FRU, etc. being removedfor clarity). As just one example, the first 1212 ₁, 1612 ₁ of the firstand second blind mate connectors 1212, 1612 may facilitate network andserial data connections between the FRU 1312, the PCB of the first blindmate connector 1212 ₁, the central management controller, and/or otherFRUs 1312; the second 1212 ₂, 1612 ₂ of the first and second blind mateconnectors 1212, 1612 may facilitate fiber optic connections between theFRU 1312, the central management controller, and/or other FRUs; andthird and fourth 1212 ₃, 1612 ₂ and 1212 ₄, 1612 ₂ of the first andsecond blind mate connectors 1212, 1612 may facilitate power connectionsbetween the FRU 1312 and PDUs of the rack 1300.

It will be readily appreciated that many additions and/or deviations maybe made from the specific embodiments disclosed in the specificationwithout departing from the spirit and scope of the invention. Theillustrations and discussion herein has only been provided to assist thereader in understanding the various aspects of the present disclosure.In some arrangements, one of the interface portions 1244, 1644 of acorresponding pair of first and second blind mate connectors 1212, 1612may not necessarily extend through its corresponding receiving aperture1240, 1640 and may be merely aligned with the respective receivingaperture 1240, 1640.

In one arrangement, and while the frame center 120 has been disclosed asgenerally facilitating communications (e.g., as a switch) between theFRUs 112 in relation to out of band management, another switch (e.g.,InfiniBand) may be provided to facilitate communications between theFRUs 112 and devices or networks outside of the frame 100. That is,while the FRUs 112 may be interconnected to the frame center 120 (e.g.,via interfacing of connectors 128, 132) for OOB management of the FRUs112, the FRUs 112 may also be appropriately interconnected to anInfiniBand or other type of switch for other types of communicationsand/or data transfers (e.g., video-conferencing traffic). In anotherembodiment, more than one frame manager may exist within the frame. Forinstance, while the frame center 120 may run a frame manager for OOBmanagement of FRUs (e.g., in relation to powering up, hot-swapping, andthe like), one of the FRUs 112 may run another frame manager thatadministers higher level managerial tasks within the frame 100.

In one arrangement, a FRU 112/412 may be appropriately locked in itsparticular receiving bay in the rack 104/404 and thus unable to beunlocked and removed until the service processor 160 and/or framemanager 168 has performed any necessary OOB management routines. Inanother arrangement, the service processor 160 and/or frame manager 168may be configured to automatically begin OOB management routines (e.g.,an offlining processes) upon detection of a pulling or tugging on a FRU112/412 in an attempt to remove the FRU 112/412 (e.g., as an alternativeto depressing a button 182 on a corresponding frame arm 116/416). Inthis regard, the FRU 112/412 may be locked in its receiving bay of therack 104/404 until the OOB management routines have been completed.

Furthermore, one or more various combinations of the above discussedarrangements and embodiments are also envisioned. For instance, whileFIG. 11 illustrates each of the first and second frames 400, 404 beingin the form of frame 100, at least one of the first and second frames400, 404 could be in the form of the frame 100′ of FIG. 10 whereby a FRU112′ in the form of an enclosure of chassis includes a plurality of FRUs112″ in the form of blade servers. As another example, the attachmentportion 708 of the adapter 700 could have one or more additionalreceiving apertures for receiving additional connectors 432 which may beconfigured to electrically interface with one or more additionalcorresponding connectors 428 of the frame arm 416. As a further example,the adapter 900 and frame arm 1016 could be utilized for FRUs of othersizes (e.g., 2U, 3U, etc.).

Embodiments disclosed herein can be implemented as one or more computerprogram products, i.e., one or more modules of computer programinstructions encoded on a computer-readable medium for execution by, orto control the operation of, data processing apparatus. For example, theframe manager 168 may be provided in such computer-readable medium ofthe frame center 120, one of the FRUs 112, and/or the like, and executedby a processor or processing engine (not shown) of the FRU 112. Asanother example, the logic or software of the frame center 120responsible for accessing the manager PROM image 148 and routingcommunications within the frame 100 may be provided in suchcomputer-readable medium of the frame center 120 (e.g., memory 144) andexecuted by a processor or processing engine (not shown) of the framecenter 120 (not shown). The computer-readable medium can be amachine-readable storage device, a machine-readable storage substrate, anon-volatile memory device, a composition of matter affecting amachine-readable propagated signal, or a combination of one or more ofthem. In this regard, the frame 100 may encompass one or moreapparatuses, devices, and machines for processing data, including by wayof example a programmable processor, a computer, or multiple processorsor computers. In addition to hardware, the frame 100 may include codethat creates an execution environment for the computer program inquestion, e.g., code that constitutes processor firmware, a protocolstack, a database management system, an operating system, or acombination of one or more of them.

A computer program (also known as a program, software, softwareapplication, script, or code) used to provide any of the functionalitiesdescribed herein (e.g., managing FRUs 112, routing communications, andthe like) can be written in any appropriate form of programming languageincluding compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program does not necessarily correspond to a file in a filesystem. A program can be stored in a portion of a file that holds otherprograms or data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit). Processors suitable for theexecution of a computer program may include, by way of example, bothgeneral and special purpose microprocessors, and any one or moreprocessors of any kind of digital computer. Generally, a processor willreceive instructions and data from a read-only memory or a random accessmemory or both. Generally, the elements of a computer are one or moreprocessors for performing instructions and one or more memory devicesfor storing instructions and data. The techniques described herein maybe implemented by a computer system configured to provide thefunctionality described.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular embodiments of the disclosure. Furthermore, certain featuresthat are described in this specification in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and/or parallelprocessing may be advantageous. Moreover, the separation of varioussystem components in the embodiments described above should not beunderstood as requiring such separation in all embodiments, and itshould be understood that the described program components and systemscan generally be integrated together in a single software and/orhardware product or packaged into multiple software and/or hardwareproducts.

The above described embodiments including the preferred embodiment andthe best mode of the invention known to the inventor at the time offiling are given by illustrative examples only.

We claim:
 1. A storage rack for supporting electronic devices,comprising: a plurality of front vertical support pillars; a pluralityof rear vertical support pillars that are spaced from the plurality offront support pillars; a plurality of pairs of first rail assembliesrigidly interconnecting the plurality of front and rear vertical supportpillars; and a plurality of first housings, wherein each first housingrigidly interconnects a first rail assembly of a respective one of theplurality of pairs of first rail assemblies to an opposite second railassembly of the respective one of the plurality of pairs of first railassemblies, and wherein each first housing includes one or more firstblind mate connectors fixable thereto.
 2. The storage rack of claim 1,wherein each first housing includes: a pair of side members, wherein afirst side member of the pair of side members of the first housing isrigidly interfaceable with the first rail assembly of the respective oneof the plurality of pairs of first rail assemblies, and wherein a secondside member of the pair of side members of the first housing is rigidlyinterfaceable with the second rail assembly of the respective one of theplurality of pairs of first rail assemblies; and an attachment portionrigidly interconnecting the first and second side members of the firsthousing, wherein the attachment portion rigidly supports the one or morefirst blind mate connectors of the first housing.
 3. The storage rack ofclaim 1, wherein the first and second rail assemblies of each pair offirst rail assemblies each include: a base member having first andsecond opposite edges; a first containment member extending from thefirst edge of the base member; and a second containment member extendingfrom the second edge of the base member, wherein each first housing isreceived between the first and second containment members of the firstand second rail assemblies of the respective one of the plurality ofrail assemblies.
 4. The storage rack of claim 1, further including: aframe including opposite front and rear access openings, wherein theplurality of front vertical support pillars are disposed adjacent thefront access opening, wherein the plurality of rear vertical supportpillars are disposed between the rear access opening and the frontaccess opening, and wherein the plurality of first housings are disposedbetween the plurality of rear vertical support pillars and the rearaccess opening.
 5. The storage rack of claim 2, wherein the attachmentportion of the first housing includes: a tray including first and secondopposite ends and top and bottom surfaces between the first and secondends, wherein the first end of the tray of the first housing is attachedto the first side member of the first housing and the second end of thetray of the first housing is attached to the second side member of thefirst housing; and a wall protruding from top surface of the tray of thefirst housing, wherein the one or more first blind mate connectorsextend through the wall of the first housing.
 6. The storage rack ofclaim 3, wherein one of each first housing or each respective one of thepair of first rail assemblies includes a fastener and the other of eachfirst housing or each respective one of the pair of first railassemblies includes an aperture that is configured to receive thefastener to non-movably lock the first housing to the respective one ofthe pair of first rail assemblies.
 7. The storage rack of claim 5,wherein a first of the one or more first blind mate connectors isslidably receivable along the tray and into the wall of the firsthousing.
 8. The storage rack of claim 4, further including: a pluralityof pairs of second rail assemblies, wherein each pair of second railassemblies is slidably engageable with a respective one of the pluralityof pairs of first rail assemblies; and a plurality of second housings,wherein each second housing rigidly interconnects a first rail assemblyof a respective one of the plurality of pairs of second rail assembliesto an opposite second rail assembly of the respective one of theplurality of pairs of second rail assemblies, and wherein each secondhousing is configured to engage with a respective one of the pluralityof first housings when a corresponding one of the plurality of pairs ofsecond rail assemblies slidably engages with a respective one of theplurality of pairs of first rail assemblies.
 9. The storage rack ofclaim 7, wherein the tray of the first housing includes first and secondspaced guide members, wherein the first of the one or more first blindmate connectors is slidably received between the first and second spacedguide members and into the wall of the first housing.
 10. The storagerack of claim 7, wherein the wall includes first and second spacedslots, and wherein the first of the one or more first blind mateconnectors includes first and second spaced pins that are slidablyreceived in the first and second spaced slots.
 11. The storage rack ofclaim 4, wherein the aperture is disposed through at least one of thefirst and second containment members of the respective one of the pairof first rail assemblies, and wherein the fastener is a spring loadedpin attached to the first housing.
 12. The storage rack of claim 8,wherein each second housing includes one or more second blind mateconnectors fixable thereto, and wherein the one or more second blindmate connectors electrically connect with the one or more first blindmate connectors when the respective one of the plurality of pairs ofsecond rail assemblies slidably engages with the respective one of theplurality of pairs of first rail assemblies.
 13. The storage rack ofclaim 10, wherein the first slot includes a first longitudinal axis,wherein the second slot include a second longitudinal axis, and whereinthe first and second longitudinal axes are perpendicular.
 14. Thestorage rack of claim 12, further including: a plurality of fieldreplaceable units (FRUs), wherein each FRU is rigidly connected to thefirst and second rail assemblies of a respective one of the plurality ofpairs of second rail assemblies, wherein each FRU is electricallyconnected to the one or more second blind mate connectors of the one ofthe second housings that is rigidly interconnected to the first andsecond rail assemblies of the respective one of the plurality of pairsof second rail assemblies, and wherein the electrical connection betweenthe one or more second blind mate connectors and the one or more firstblind mate connectors electrically connects the FRU with a centralmanagement controller of the storage rack.
 15. The storage rack of claim12, wherein each second housing includes: a pair of side members,wherein a first side member of the pair of side members of the secondhousing is rigidly interfaceable with the first rail assembly of therespective one of the plurality of pairs of second rail assemblies, andwherein a second side member of the pair of side members of the secondhousing is rigidly interfaceable with the second rail assembly of therespective one of the plurality of pairs of second rail assemblies; andan attachment portion rigidly interconnecting the first and second sidemembers of the second housing, wherein the attachment portion rigidlysupports the one or more second blind mate connectors of the secondhousing, and wherein the attachment portion of the second housingincludes: a tray including first and second opposite ends and top andbottom surfaces between the first and second ends of the second housing,wherein the first end of the tray of the second housing is attached tothe first side member of the second housing and the second end of thetray of the second housing is attached to the second side member of thesecond housing; and a wall protruding from top surface of the tray ofthe second housing, wherein the one or more second blind mate connectorsextend through the wall of the second housing.
 16. The storage rack ofclaim 13, wherein the tray of the first housing includes first andsecond spaced guide members, wherein the first of the one or more firstblind mate connectors is slidably received between the first and secondspaced guide members and into the wall of the first housing.
 17. A nodeof a backplane of a storage rack for computing devices that isconfigured to be mounted adjacent a rear of a bay of the storage rackand electrically interconnect with a computing device received in thebay, the node comprising: a housing including a pair of side members andan attachment portion rigidly interconnecting the first and second sidemembers, wherein the housing is configured to rigidly interconnect firstand second rail assemblies defining the bay in the storage rack, andwherein the attachment portion includes: a tray including first andsecond opposite ends and top and bottom surfaces between the first andsecond ends, wherein the first end of the tray is attached to the firstside member and the second end of the tray is attached to the secondside member; and a wall protruding from top surface of the tray; and oneor more blind mate connectors extending through the wall of the housing.18. The node of claim 17, wherein a first of the one or more blind mateconnectors is slidably receivable between first and second guide membersof the tray and into the wall of the housing.
 19. The node of claim 18,wherein the wall includes a first alignment slot extending along a firstlongitudinal axis and a second alignment slot extending along a secondlongitudinal axis that is perpendicular to the first longitudinal axis,and wherein the first of the one or more blind mate connectors includesfirst and second spaced alignment pins that are slidably receivable inthe first and second spaced alignment slots.
 20. A method of adapting astorage rack to facilitate out of band (00B) management of fieldreplaceable units (FRUs) mounted within the storage rack by a centralmanagement controller connected to the computing rack, comprising:mounting a plurality of pairs of first rail assemblies to front and rearvertical support pillars of the storage rack; and rigidly securing oneof a plurality of housings to first and second rail assemblies of eachpair of first rail assemblies, wherein each housing includes: a circuitboard comprising a memory storing data indicating a location of thehousing relative to other ones of the plurality of housings of thestorage rack; and a connector electrically interconnected to the circuitboard and configured to interface with a corresponding connector of aFRU to allow for OOB management of the FRU by the central managementcontroller.